Description
In Materiel Management, Quality Control, customer need the capability to view and search Service Performed actions.

Recommended
Recommend adding Service Performed to the main GRID line in Quality Control.

Mission Critical
Yes, because customer needs visibility of work performed by M&U personnel.

Benefits
The benefit is this process will reduce errors make it possible for QC to track maintenance performed by M&U personnel.

Users
All

Completed - Release 3.0 - 15 May 2015

To remove an asset (largest one), we would have to check all of the following tables for possible corresponding records before we could actually remove the asset from Asset Master. There would be a need to incorporate business logic into the routines to determine what to do if things are not closed out, etc. For example: ?What if a project is not closed, do we remove? ?It believe it would be fine if the Site Id was abandoned and we knew there were no financial reporting to contend with, but if the Site Id is active, and the request was to only remove a specific UIC and the UIC had active assets, that could become an issue with financial reporting. Recommended solution: 1. Remove improvement depreciation rows associated with improvements associated with Asset 2. Remove improvement ancillary costs rows associated with improvements associated with Asset 3. Remove improvement acquisition rows associated with improvements associated with Asset 4. Remove improvement "Attachments" if they are permitted. 5. Remove improvements from CIP Asset 6. Remove improvement 7. Remove Work Orders 8. Possibly some FAST tables 9. Remove Maintenance Activity Master 10. Remove Due Out 11. Remove Due In 12. Remove Asset Ancillary Costs 13. Remove Asset "Attachments" 14. Remove Asset Utilization 15. Remove CIP Asset 16. Remove UII 17. Remove Depreciation 18. Remove Asset Acquisition 19. Remove Asset Master 20. Remove stuff from CFO tables.

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