The field "Receive Dt" is required on the Materiel Mgmt-->Receiving but we cannot view this field on  asset inquiry. Received date is an audit requirement for General Equipment Assets.

 

Add a "Receive Dt"  column in the Inventory Update Manager, ICN Inventory, and Inventory Activity.  Add the ability to edit the "Receive Dt" field in the Inventory Update Manager.

 

 

 

DOD requirement.

 

Frequency: Hourly

 

DoD Components are required to record and maintain data element "Date Placed in Service"  in their respective APSRs as stated in DoDI 5000.64 and the USSOCOM Directive 700-2.

 

Add a "Date Placed in Service" required field during the receiving process.  Add a "Date Placed in Service"  column in the Inventory Update Manager, ICN Inventory, and Inventory Activity.  Add the ability to edit the "Date Placed in Service" field in the Inventory Update Manager.

 

 

DOD requirement.

 

Frequency: Hourly

 

Currently the Force System Management Module only interfaces with the Property accountability module which is used to determine the DAF authorizations to build requirements. However, we require the capability to establish requirements for items that do not fall into the Class VII category and in some cases consumable materiel.

 

Establish the capability to create FSM authorizations for assets managed in the Warehouse module.

 

IAW AFI 23-101 The DAF is required to maintain Class II and Class IX materiel to support the wing's deployment requirements and report readiness capabilities. Establishing authorizations for materiel provides the DAF the capability to ensure the posture of materiel is appropriately aligned to and determine overages and shortfalls for future procurements or reposturing.  

 

This would provide Senior leadership visibility of all DAF stockage/storage requirements and current posture to make strategic level decision.

 

Frequency: Daily

 

According to SOCOM Directive 700-2 we are to conduct monthly inventory of All controlled, classified or sensitive Controlled Inventory Item Code (CIIC) items with codes 1-6, 8-9, P, Q, R, S, Y (including all Night Vision Devices and Navigational Devices) regardless of cost will be inventoried on a monthly basis.

 

Add additional selection parameters to the Issued Inventory under the Details section with the ability to select multiple Stock Numbers, CIIC codes, Commodity types, and Issued Warehouse.  Enable the user to save selected stock numbers, CIIC codes, commodity types, and Issued Warehouse with the ability to name the saved selection.  Enable the user to edit and delete saved selections.  Enable the user to select a previously saved selection which will auto-populate Stock Number, CIIC , Commodity Types, and Issued Warehouse.  Add a Select All UIC's under Select UIC to print all (multiple) issued inventory.  The Stock Number, CIIC , and Commodity Type selection is default to all.

 

N/A

 

SOCOM requirement.

 

Frequency:
Hourly

 

The current problem is we have some members in DPAS that have multiple issues from different warehouses/locations.  We need to be able to differential between the issues so we are able to return equipment to the proper warehouse/location,  Proposed solution would be to have a way to designate the exact items from a particular warehouse/location. Possible Fix would be to add the Master Issue List(MIL) option on the individual return so you are able to pull the exact items the individual was issued from a particular warehouse/location.

 

Recommendation is to add a MIL option on the individual return so you are able to pull the exact items the individual was issued from a particular warehouse/location.  Inserting the MIL, would allow the CSR to pull up the desired gear list to return.

 

Yes, because the Consolidated Storage Program (CSP) goal is to have an accurate inventory and with this functionality the customer service representatives (CSRs) will be able to conduct returns into the system with more truthful data.  

 

Having this capability will help all warehouses improve on inventory accuracy across the enterprise.  

 

Frequency: Daily

 

DPAS continues to expand its customer base.  As part of this expansion, there is a requirement to support shipments to foreign governments.  These shipments are assigned a MAPAC (Military Assistance Program Address Code) which is equivalent to a DoDAAC.  Today, DPAS permits the manual entry of a MAPAC, but there is no validation that what was entered is a valid MAPAC.  DPAS provides a data feed of MAPACs similar to the DoDAAC data feed.  This SCR is requesting DPAS add the MAPAC to its DLA DAAS agreement and provide for import / selection / validation of MAPACS from the master list of MAPACs.

 

Import MAPACs, provide the capability to select / validate a MAPAC that is entered to the master list of MAPACs. This change would apply to Materiel Mgmt, (Customer Requisition), Warehouse (Materiel Release Order).  The requisition service would need a change to support MAPAC validate if it supports Military Assistance Program ordering. Asset Disposition in PA  that utilizes the Address Directory will likely need to support Military Assistance issues.

 

This change improves / reduces the opportunity of error in the entry of a Military Assistance Program Address Code.  

 

Improves the overall entry and validation of a Military Assistance Program Address Code.  

 

Frequency: Weekly

 

DPAS designed the Contractor / Contract processes for use with the Materiel Mgmt. and Warehouse Mgmt. applications to be enterprise.  Once it is created, it is available for all to use. While this may be good (enter once / use by all), a user can also change the entries making them anything they want it to be not knowing the impact to other DPAS users.  Providing an automated process that does not require Help desk support to correct incorrect data is good, but there can be negative consequences if not properly managed. The impact could result in be materiel on loan to a contractor be re-assigned to a different contract / contractor without the user knowing their data was changed.  

 

It is recommended that DPAS review these processes for: 1) Restricting changes to those organizations that created them, 2) Notify the user who is making the update that the record they are updating is currently in use by other organizations, thus their change could impact the other organization's data and 3)  notify all organizations that are using the record that was changed of the change. It is also recommended that there be consideration given to enabling an organization to identify contractor / contracts that they are using rather than having to see all contractors / contractors that have been entered.  For example:  A west coast organization that purchases materiel from LOWES has no need to see LOWES (CAGEs) that do not reside within their proximity. Having the ability to restrict the list to those an organization users will reduce the time required to enter a record (less data to review / select) and reduce the chance of selecting an incorrect value.

 

This SCR results from a change that occurred within DPAS production by one organization that was not aware that contractor / contract data was enterprise.  They needed a new contractor and contract.  Seeing ones they were not using, they modified them to be something completely different which impacted another organization's data that established the records and were in use.  They didn't know their data was realigned to a different contractor / contract when the other organization hijacked their records. A change like this also impacts PIEE GFP reporting as the materiel is now assigned to an incorrect contract / contractor.

 

This solution enhances accuracy and may prevent an unwanted change that could take a significant amount of time to unravel and return the data to its correct state.  The impact of an enterprise change by an unknowing user the size of DPAS with a diverse user base could have a catastrophic impact to another organization's data that could take a significant effort to undo.

 

Frequency: Daily

 

According to SOCOM Directive 700-2 we are to conduct monthly inventory of All controlled, classified or sensitive Controlled Inventory Item Code (CIIC) items with codes 1-6, 8-9, P, Q, R, S, Y (including all Night Vision Devices and Navigational Devices) regardless of cost will be inventoried on a monthly basis.

 

During the creation of physical inventory add an Inv Mode to create a custom inventory selection of multiple Stock Numbers, CIIC codes, and a Type Asset Codes.  Enable the user to save selected stock numbers and CIIC codes with the ability to name the saved selection.  Enable the user to edit and delete saved selections.  Enable the user to select a previously saved selection which will auto-populate Stock Number, CIIC , and TAC.

 

 

 

SOCOM requirement.

 

Frequency: Hourly

 

The Application Administrator role/user tier is a bit of a misnomer. Additionally, in DLA J64 they refer to our privileged users (Jonathan Gillette, John O'Connor, Dave Czar, etc.) as App Admin but they have no relation to the Application Admin as it is defined in DPAS. For the sake of clarity internally and during audit it would be helpful to change the name of this role. With this change, updating the support url (https://dpas.dape.dla.mil/admin/ ) would be a good idea as since  "admin" implies privileged access to the system.

 

"Application Administrator" role/user tier could be renamed to "Application Support" and the url for the support site could be changed from "https://dpas.dape.dla.mil/admin/" to "https://dpas.dape.dla.mil/support/".

 

The change will assist with the audit support team's goal of clarifying DPAS processes and it will alleviate questions and confusion from the auditors each year.

 

Less questions/confusion during audit and internally when discussing this role.

 

Frequency: Hourly

 

Inventory Activity only shows activity of an asset during the time frame that the asset was attached to the respective warehouse.

 

Open up view capability to show entire asset inventory activity within the LP regardless of where the asset resides for all users.

 

 

 

Allows users to view the full cradle to grave history of an asset to conduct research and documentation for record keeping.