Description
IAW U.S. GAO Gov't Operations Internal Control Management and Evaluation Tool, Report GAO-01-1008C (page 40) to maintain a property separation of duties and appropriate internal controls, secondary reviews of APSR entries need to be performed by personnel with a proper level of authority to the work being performed. The reviewing/approving official is responsible for checking the accuracy of the APSR entry and the adequacy and validity of the source supporting documentation. Navy Budget Submitting Offices must be able to demonstrate secondary review authority designation and approval of APSR entry approval before the asset is added or removed from the APSR.

Recommended
Create an automated work flow process in DPAS to permit supervisory role (with DPAS e-Learning training) to implement an automated approval process for asset receiving, transfer and disposition transactions. This new approval process is required "before" assets are added to or removed from the APSR by the Property Officer (Navy PPM role 1024). Add Inquiry/Asset Management /Asset Inquiry and Asset Activity (history) search values and fields necessary to generate reports to demonstrate secondary review/approval.

Mission Critical
Mandated by OASN Financial Management and Comptroller Memo July 07, 2014. Please estimate and forward a ROM for Navy funding and budget purposes.

Benefits
Supports FIAR accountability and financial reporting initiatives.

Users
Yes to all Agencies. 

Joe Stossel comment, 2/24/2015 - Need more research to determine if this is truly required. This would greatly increase the time it takes to add assets to DPAS and really make the users unhappy.

21 Aug 2019 – cancelled per Kevin Callahan
No Longer Required.

DISA is unable to fully implement the WAWF to DPAS interface for IUID due to its global presence. Currently equipment is deployed directly from the vendor to DISA's nodes for installation. These nodes are housed and managed by the Army, Air Force, Navy/ Marine Corp, and DoD. DISA has no staffing or organizations at these locations. The equipment is hand receipted to service member at the Non-DISA site. The WAWF to DPAS interface operates on the shipping DoDDAC. The DoDDAC's are not DISA's therefore the current structure provides no benefit to enhance auditability. Recommended solution: Develop a solution where DoDDACs can be assigned at the hand receipt level. This will allow for DISA to establish DoDDACs for all the locations where DISA's equipment resides. When equipment is shipped from the vendor to the Non-DISA site, DISA APO's would be able to identify the equipment within the DPAS due in module and process the equipment onto the hand receipt. Customer priority: 3 Joe Stossel comment, 2/24/2015 -?Discussed an alternate method of determining WAWF transactions to send to DPAS with the WAWF experts.??This may get these transactions for DISA.??It is based on who funds the purchase not the shipping.

Currently, DISA is not relying on the DPAS calculation of depreciation for its financial statements. ?Historically, assets were not captured accurately in DPAS so DISA?s accounting function (CFE) has used an alternative method of depreciation based on the funding used to purchase the asset. ?A Material Internal Control Weakness was identified in the FY12 independent audit report of the DISA general fund financial statement regarding property. DISA?s external auditors identified the following material weakness: DISA is unable to capture accurate asset activation dates due in part to: (i) an inability to classify capital asset acquisitions (ii) the grouping of physical/intangible system assets, and (iii) the overall lack of detailed asset listings. DISA is in the process of implementing improved controls to address the material weakness and use DPAS to calculate depreciation for the financial statements. ?However, due to the complex nature of DISA?s operations, it was decided by management that using the mid-year convention for depreciation is an attainable goal which will allow the agency to conform to the DoD FMR using an acceptable depreciation method. ?Currently, DPAS does not allow for the use of a mid-year convention. See Attached Decision Document. Recommended solution: Add an option to DPAS allowing for use of the mid-year convention depreciation method as stated in the DoD FMR (DoD 7000.14-R Section 060205.G2): ?Under the Mid-Year Convention Method, six months of depreciation is computed and expensed in the first and last year of an asset?s useful life, regardless of the actual month the asset was placed in, or removed from, service.? ?Implementation of this method in DPAS would mean that an asset?s ?activation? date for depreciation will always be 3/31 of the fiscal year in which the asset was placed into service. ?For assets using the mid-year convention, calculation of depreciation should occur once per year at the end of the fiscal year on 9/30. Preferred Solution: DISA intends to use the mid-year convention only for assets purchased using the General Fund. ?From the DPAS user?s perspective, they may enter an ?in-service? date but should not enter a date used for activation of depreciation. ?The system should automatically apply an activation date of 3/31 and calculate depreciation once per year. Alternative Solution (short-term): Allow recording of activation dates that are prior to acquisition dates. If users can enter 3/31 as the activation date regardless of whether the asset was purchased later in the fiscal year, depreciation can be calculated using the mid-year convention. Customer priority: 2

Description
"Network Detection Tools" As their primary objective the DISA requests that an interface be established between their network configuration change management (NCCM) system and DPAS in order to better know which assets are connected to the network and exist in DPAS. Secondarily, know which software and firmware are installed on each device in order to better manage their software license compliance.

Recommended solution
This process begins on the customer's network when the customer executes their Network Discovery Tool, NDT. This is a function of the customers Network Configuration and Change Management (NCCM) system. The NDT may be run for a variety of reasons using any number of filters. It is not anticipated DPAS receive all assets/software, on every run. The results of the network discovery are passed through the GEX in the form of one or more XML files. Using GEX serves to isolate the systems and makes it a hardware/software independent interface.
This interface would work similar to the automated inventory or RTLS programs in that a file would be received by DPAS and routed to either a hardware auto reconciliation program or a software auto reconciliation program. The automated reconciliation program would log and produce results. Anomalies are then made available to the operator in order to resolve manually.
High Level Task:

1. Establish a relation between the NDT and the DPAS database
2. Establish a GEX connection
3. Establish the data elements and structure of the XML file
4. Add the necessary tables to support the reconciliation
5. Add an NDT Director program to route the hardware data and software data
6. Add an NDT Auto Reconciliation program to produce exceptions
7. Add an NDT Manual reconciliation program to allow the operator to match records not found in DPAS
8. Modify the pending transactions, asset receiving, asset update, asset transfer, asset disposal, to pass a transaction identity to each called sub-programs.
9. Modify the current inventory process to conduct NDT inventories.
10. Add NDT inquiry for assets on DPAS
11. Add NDT reporting for the auto reconciliation
12. Add NDT reporting of DPAS Assets
13. Conduct the development in at least two phases. The first of which is to accommodate the asset side of the interface, as this satisfies the primary requirement. In the second phase establish the interface to the existing IT Software management program.

Mission Critical
Yes, this is mission critical for the DISA. They are investing money and effort into modernizing their network management and need to keep DPAS as their accountable property system.

Benefits
This change allows DISA to gain greater visibility of their assets and would greatly reduce the time required to conduct manual inventories.

Users
Any user who can provide the necessary data elements from their NDT should be able to make use of this interface.

Partially Completed – Release 2023.2.7 – 30 June 2023

Partially Completed – Release 2023.3.2 – 28 July 2023 

(SCR created on 5/21/2014) The process to Dispatch and Return an asset would be more efficient if the process could be accomplished utilizing a Hand Held Device. Create processes for the DPAS Hand Held Devices to permit the Dispatch and Return of assets utilizing the Hand Held Device.? Being able to scan the users CAC and then the asset being dispatched or returned would permit an efficient process for the Fleet Manager.

Description
Need a way to mark an active asset as "Pending Disposal."

Recommended
Recommend adding a check block to an active asset record that would be available via the Asset Management / Update process to indicate the asset is Pending Disposal.

Mission Critical
FIAR critical.

Benefits
Supports FIAR review/audit of 'disposition' transactions. Provides the ability to compare asset marked as Pending Disposal to the asset actually disposed to DLA Disposition Services. This would help identify assets that need to be removed from the APSR and would also help identify assets that require disposition to DLA Disposition Services.

Users
Yes to all Agencies.

Customer priority
4

Joe Stossel comment, 2/24/2015
Should be able to mark the asset as excess with it automatically being sent to DRMO
can be worked as part of the DAISY replacement.

Joe Stossel comment, 8/10/2015
should be able to mark assets as excess without automatically reporting to DRMO.
This SCR could be worked with the RBI Interface

07Nov2018 – cancelled per Kevin Callahan

Description
The Agency Pre-Definded report titled "Capital Code N or S Errors" does not contain the necessary fields to adequately identify errors due to the OUSD Capitalization threshold changes went into effect 01 October 2013.

Recommended
Add the following fields to the Agency Predefined Report - Capital Code N or S Error report:

• Activation Dt
• Acq Dt
• Local Rcpt Dt

Mission Critical
This report is required to identify capital assets incorrectly coded and this information is used to create Navy Monthly Metric reports which is sent to Navy Major Commands for corrective actions.

Benefits
Will permit Navy to correctly depreciate capital equipment in support of FIAR efforts.

Users
All Navy Users

Joe Stossel comment, 2/25/2015 -
Same as SCR 00662.

From Randy For SCR 00609, I added the following fields to WCUSS06 Agency Defined Report:

• Accumd Deprn
• Acq Dt
• Local Rcpt Dt
• Origl In Svc Dt
• Activation Dt.

I named the USP a little better to make it more identifiable.
I recommend removing the current one from the database andreplacing it with this one.
For the pre-built report table, I recommend we update the info for the current one to the following and ensure all Site Ids in the dpas.dbo.site table have it.

• rpt_nm - AssetsWithCapCdNOrS-SiteId
• rpt_desc - Capital Code N or S Errors by Site Id
• rpt_std_prcdr - uspCustomRptAssetsWithCapCdNOrS_Site_WCUSS06

I have also created a new Pre-Build Report that will run at Agency Level that will need to be inserted into the Pre-Built report table for every Agency we have in the dpas.dbo.agencytable.
The CI Number is WCUSS45.
I created the FRD and have added to the FRD Archive in SharePoint.

• rpt_nm -AssetsWithCapCdNOrS-Agency
• rpt_desc - The extract will display all active assets with a Capital Code or N or S Errors for the Agency of the Site Id the user is logged into at time of run.
• rpt_std_prcdr - uspCustomRptAssetsWithCapCdNOrS_Agency_WCUSS45
• setng_lvl_cd - 5

Note: I do not have permission to create a store procedure, so I don't know if these 2 USPs will actually build.
I would recommend testing.

Completed - Release 4.0 - 29 April 2016

Description
Currently I am unable to upload documents to items using a mass update function.
I have a requisition document for 450 items.
I should be able to add this document to all of the items at once instead of individually. This functionality is available when conducting disposition/DRMO.

Recommended
Make the capability to add documents an available selection on the mass update page.

Mission Critical
Yes it is mandated. DON Office of Financial Operations (FMO) Plan of Action Milestones (PoAM) requires testable audit-ability for individual items. It isn't feasible for me to individually add a requisition document to each item individually.

Benefits
Greatly reduces time. I do not want to individually load this requisition document to each of these 450 items one at a time. It would save significant time to only add it once.

Users
Yes. When acquiring a group of similar items (a new enterprise computer contract) the property book officer could add required documents to DPAS in a short amount of time.

Joe Stossel comment, 2/24/2015 -
same as SCR 00586 and 00661

The management messages only provides access to the message that applies to that particular user instead of providing informational access to all users assigned to that UIC. Recommended solution: Recommend the Management Messages be accessible to all users with UIC access and above (APO/PA) to be able to view those messages which pertain to that Accountable UIC/UIC. This will also allow access for the managers for that Accountable activity to ensure the job is being accomplished in a timely manner. Customer priority: 1

Change Requested:Federal Information Security Management Act (FISMA) Control AS-2.4.2 states "Owners periodically review access to ensure continued appropriateness." Our Account Management procedures state the Information Owners need to review user access biannually to ensure the access granted is appropriate. We are requesting inquiries or reports be developed so the DPAS Information Owners can review the access assigned to their users.Recommended Solution:Develop an inquiry to show the following information:User Id, Full Name, Email Address, Active, Last Login Date, Expiration date, Is Suspended, Is Expired, Established By, Established By Dt/Time, Last Updated By, Logistics Program, Region, Site, Warehouse, every role assigned for each Warehouse, Training Completion Date for each role and every Commodity Type for each Warehouse.If the user?s access is driven at the level (Logistics Program, Region, Site & Warehouse) where the roles are assigned, then we will need a way to reflect that information as well. For example, on the PA side this is the user?s Level of Access. On the Warehouse side it seems the user?s access varies depending on what level the roles are assigned to the user?s account.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.Joe Stossel comment, 2/24/2015 - Is this the same as SCR 603??