Currently MDA has four assets valued at $102,000.00 that were received in November of 2014 that are on the Capital Asset Report. According to the DPAS developers, these assets were a part of a Construction in Progress (CIP) project. ?The Accountable UIC should have the ability to change the Capital Code even if the assets were a part of a CIP Project. Recommended solution:?Allow users at the Agency level the ability to change the Capital Code when necessary, no matter if the asset is a part of a CIP project or not.

11 Mar 2021 – cancelled per Jack Sanders
No Longer Needed.

Description
DPAS warehouse system will not allow a Individual Issue Location to be set up as a default return location. MARFORSOC MCIF requests the ability to update Individual Issue Locations in DPAS to include a return under Location Type Cd.

Recommended
Have ability to update Individual Issue Locations to be set up as a default return locations.

Mission Critical

Benefits
This would improve the return accuracy and accountability. Default return locations will allow for selected equipment to go directly back the Individual issue location physically and in the system. This would not take away the chance of error placing equipment into a in-transit location then having to move it back to Individual Issue location.

Users
This would impact all users if they chose to make default locations.

Completed - Release 3.0 - 15 May 2015

New DPAS Statistics graphs for the M&U Category Sidebar. ?Also have the graphs downloadable to a .ppt and .pdf. Recommended solution: see attachment

Description
There are DPAS tables shared between modules (Address and Utilization) and this request is to include Attribute as well.

Recommended Solution
Once the Attribute Template is selected in the Catalog, make it available as a tab in the M&U Maintenance Asset Master.
This will allow M&U users to utilize Attributes for fields maintenance related. Also provide a view of the data to Dispatch.

This data is needed to select the correct vehicle.
Example of an existing system is attached showing make, model, fuel type, mileage, etc. Create a screen for M&U to modify the Attributes and add to Role(s).

Mission Critical
N/A

Benefits
Allow maintenance managers the opportunity to create fields related more to M&U and have access to load information.

Users

Completed - Release 3.2 - 06 January 2016

In Materiel Management, Quality Control, customer request the serial number be placed on the Main Grid line.

11 Mar 2021 – cancelled per Jack Sanders
No Longer Needed.

When doing an asset transfer in the PA module the user should be able to sort by LIN/TAMCN, Loan Code, Fund Code or Stock Number. When a user is doing a UIC to UIC transfer they can only transfer one LIN/TAMCN at a time, so it would be nice to be able sort by LIN/TAMCN so they can select all like LIN/TAMCN they want to transfer without paging through all the assets looking for like LIN/TAMCNs. Same for Loan Cd, they cannot transfer Loan Code types other than G, so it would be nice to sort and find those quickly. User needs to transfer like fund codes at times too, so that sort would be good too. Having the stock number sorted would be good also, so they can be in numerical order and easy to select. Recommended solution: Create sortable columns for LIN/TAMCN, Loan Code, Fund Code and Stock Number on the Asset Transfer Search Results page.

Description
The ability to assign DPAS Columbus and Leidos staff access to all warehouses without having to add each warehouse to the account separately. In PA there is a User Type Code called Application Administrator. When this User Type Code is assigned it allows enterprise access to all Site-Ids. A role is then added to the account to allow view only access at the enterprise level. Once the Application Administrator account is established no further action is required for the user to be able to see new Site-Ids added to DPAS.

Recommended
Something needs to be developed in the warehouse module that will allow enterprise data inquiry access without each warehouse having to be added to the users account. Currently there are 273 warehouses in Production. As new warehouses are added to DPAS, each DPAS Columbus and Leidos staff account must be updated to include the new warehouse. Currently, each account takes over 3 hours to create and then additional time to be maintained. We are requesting the User Type be used as a solution. This also fulfills the requirement for a clear separation of duties. The User Types could be utilized as follows:

• Standard – Used for the majority of the users. All roles but Help Desk, Security Officer and Job Schedule Manager would be available for this user type.
• Security – This is already in use. The only role that can be assigned is Security. No change is being requested.
• Application Admin – Used for DPAS Columbus and Leidos. Data Inquiry enterprise access is needed for all individuals with this user type. The roles available to this user would be Enterprise Inquiry (which would need to be created) and Admin Reports.
• Agency Coordinator – Used for USMC help desk. From talking with USMC, their help desk will need to be able to complete all transactions in the system for the caller. This would require roles assigned at the Logistic Program level with the ability to access all warehouses under the assigned LP without adding each warehouse individually. All Standard roles would be available for this user type.
• Admin Console – The only available role for this user should be Job Schedule Manager.

Mission Critical
FISMA Control ECLP-1 states: Access procedures enforce the principles of separation of duties and "least privilege." Access to privileged accounts is limited to privileged users. Use of privileged accounts is limited to privileged functions; that is, privileged users use non-privileged accounts for all non-privileged functions. This control is in addition to an appropriate security clearance and need-to-know authorization. This was an audit finding for us during our old SAS70 audit. It was the reason why the User Type Codes were developed on the PA side. The User Type Codes are in the Warehouse but the only ones in use are Standard and Security.
During the SSAE 16 audit, Control 6.39 states Access controls have been established to enforce segregation of duties. I’ve always provided the following:

• User Type Codes within the application create a clear separation of duties.
  Users’ can only be assigned one User Type Code.
  They are as follows:
  • Standard User – Used for the majority of users
  • Security Officer – Only used for DPAS User Account Management in Columbus, OH
  • Application Administrator – Assigned to the DPAS Support Desk. Inquiry only access to assist callers requiring assistance.
  • DPAS Agency Coordinator – Typically one or two users per agency. User has the ability to determine a few agency setting and inventory plans.
  • DPAS Administration Console – Used to monitor the general health of the system. Only assigned to DPAS Columbus and Leidos staff.

Benefits
It will save time for the DPAS Account Management staff and allow the DPAS Columbus and Leidos staff immediate access to all warehouses as they are added to the system. This is also required to provide the appropriate information for the upcoming SSAE 16 audit.

Users
This SCR is needed to be in compliance of the upcoming SSAE 16 audit.

Completed - Release 3.0 - 15 May 2015

Currently DPAS Account Management sees the Warehouse user accounts by going to the User Management screen. To get to this screen we go to Security Mgmt and select User. Currently there is no way to see the users by Logistics Program. I've had to generate the results on this screen and export the information and go through and manually look through the email addresses to provide user reports. This is time consuming and cumbersome.

Recommended solution
On the User Management screen, add a Search Criteria filter for Logistics Program. We get to this screen by going to Security Mgmt and selecting User.
SCR00605 is for an inquiry that shows every Logistics Program, Region, Site and Warehouse assigned to a user. In theory SCR00605 will show a user multiple times depending on the access granted. This request will only show each user one time. If they have access to two Logistics Programs then the other Logistics Program would need to be selected and they would show up under the other Logistics Program as well.
I would also like to request columns be added for Last Logistics Program, Last Region, Last Site and Last Warehouse. This information is available on the User Account Inquiry in the PA module and has proved to be beneficial. Not only on a daily basis but this is needed for conducting the annual audits. This inquiry should be available for Security and any Standard User assigned the Admin Reports Role. The user should only be able to see the results for their Logistics Program, Region, Site and Warehouse assigned, depending on the Level of Access granted.

Customer priority: 2

Monday, November 14, 2016:
Marked as included in 4.0

Description
The requirement exists for the system to breakout outstanding returnable items by individual issue, temp loan, and unit issue.
These are separate requirements, and should not appear on the same form.
More details are provided below:

• Individual Issue
  Gear issued from an individual issue facility
• Unit Issue
  Should be a UIC report, separated by the RO that drew the gear.
  Same report, but with a means to separate the RO who signed for the gear and a roll up.
• Temp Loan
  Should be a separate form as well

Recommended
It is recommended that separate reports be generated, per user/instance, in order to process returns. If an individual has equipment on temporary loan, unit issue, and individually issued to him, than those outstanding returnable items should be listed on three different reports.

Mission Critical
This is mandated due to current CSP standard operating procedure.

Benefits
Equipment accounting and the returns process will both be enhanced after this change is implemented.

Users
This will affect all CSP customers and will also affect all warehouse managers.

Completed with SCR 00757.