Description
The warehouse module has no interface to DEAMS, USSOCOM's financial reporting system of record.

Recommended
Establish an interface to between DPAS and DEAMS to pass all relevant financial data.

Mission Critical
Mission Critical

Benefits
Reduces Time/Cost, Improves accuracy, accountability and financial reporting

Users
ALL  users in DPAS.

Description
Currently 2x1.25 bar-code labels, which PFPA uses for printing from the PA module, can not be printed by the Warehouse Module(WM). Also, labels printed from the WM do not include all information required to identify bulk assets.

Recommended
It is recommended that the option of printing 2x1.25 barcode labels be added. This label should include the item desc, size, and location.

Mission Critical

Benefits
This solution would enable PFPA to utilize the same size barcode labels for the WM as is used in the PA Module and ensure that correct labels are placed on assets.

Users
This affects all WM users

**08/03/2018 - This is an UPDATE/REPLACEMENT to SCR 01313.**

Description
Currently 2x1 barcode labels, which PFPA uses for printing from the PA module, can not be printed by the Warehouse Module(WM). Also, labels printed from the WM do not include all information required to identify bulk assets.

Recommended
It is recommended that the option of printing 2x1 bar-code labels be added. This label should include the item description, size, and location.

Mission Critical

Benefits
This solution would enable PFPA to utilize the same size barcode labels as the WM and ensure that correct labels are placed on assets.

Users
This affects all WM users

**08/03/2018 - This is REPLACED by SCR 01314.**

Description
Updated form to add pertinent fields the "Dispatch To" would need to capture data. All new suggested information is in "Red".

Recommended
Added accessory issued field.  DPAS auto-populate Period of Utilization and Start Meter Reading.  Users wanted a Operators name printed field to go with signature.

Mission Critical
Information is mandated but currently listed on up to 5 different documents.  Looking to add to one form if possible.

Benefits
Paperwork and time reduction.  Can load one form to Dispatch AU for historical records.

Users
Only users that Dispatch.

Description
Expedite the closing of "Over Due Returns", it would be good to have Operators contact information available.

Recommended
When an asset is "Dispatched To" an Operator in the Dispatch AU, the Phone Nbr, Mobile Phone Nbr and Email Address pulled for the Operator/Technician AUD be available on Basic Tab.

Mission Critical
Mandated at Agency level to reduce unavailable vehicles due to lack of timely return.

Benefits
Reduces time of finding POC information. 

Users
Would benefit all users.

Description
Currently DPAS provides centralized account management when it comes to entering / maintaining DPAS User Accounts, to include what Sites/UICs, Logistics Programs/Warehouses, Maintenance Activities, and Materiel Mgmt. Programs/ICPs the user has access to.  The basis for this input is from Agency/Field appointed Information Officers IOs.
  The goal of this SCR is reduce the level of effort on the DPAS Account Mangers and the Information Owners while decreasing the time between when the action is initiated by the IO and the update is made in the system.  An example of this might be when a user is on leave, or only has drill once a month, and their account becomes suspended.  Not only are they behind in processing of their data from being away, but they must wait a day or so to have their account re-activated when the IO could accomplish the re-activation with minimal effort.   For Guard / Reserve personnel, they may not even get their account re-activated during that 2 day window.  There are other areas of a User's account that might be better severed by having the IO being able to perform the functions, such as the user requires a Commodity Type and or Role due to an employee being on emergency leave for a day that they might not otherwise have required. 

Recommended
Create a new user role in the DPAS Administration Module. The proposed role name is: Roles & Commodity Types Manager. The role will give the authorized user the ability to query user roles and account status, re-activate accounts that have been suspended, and allow the user to edit commodity types and roles by Tier (level) as needed by the Agency. The new role will not have ability to grant access to new users, re-activate deleted accounts,  or replicate any of the Account Managers responsibilities.  

Mission Critical
Mission critical to the on-going efforts to convert USSOCOM supported activities and units to DPAS. The new role gives USSOCOM ability to rapidly edit user commodity type access and in most case perform roles downgrades as required.

Benefits
Benefits all DPAS users that manage the system at the Agency or L/P levels. This new role will save time and eliminate the need to contact the help desk each time a minor change occurs in user status. With the growth of the DPAS system this change will allow the DPAS help desk to focus on system operating issues, and allow the Security team to focus on System Access requirements

Users
Impacts every user of DPAS. USSOCOM has only begun to implement WM and receives daily requests to modify user rights in PA and the WM module. This demand will grow as the system use expands.

Description
The Air Force is migrating its equipment mgmt functions that are performed within AFEMS / ILS-S to DPAS. One of those functions within ILS-S/SCS is the capability to identify and manage what equipment needs to be acquired to accomplish the AF mission.  As with any organization, there must be a systematical process of determining what Equipment to purchase when.  This is based upon mission criticality,  available funding, what the AF can possibly re-distribute among its bases.  Currently DPAS does not provide a systematic process for comparing equipment shortages to the funding available and the critically of the equipment shortage that ultimately determines the what to order and the order in which to place those orders. 

Recommended
Incorporate a process into DPAS that will systematically interact with new DPAS Allocation process and DPAS's current Authorization process to determine what the program manager is to order based upon the funds that are available.  This process will enable the Program Manger to place the order with SCS and track the funds being expended to what is available based upon the priority established through this process. 

Mission Critical
Yes.  There is a requirement that is needed to replace the existing functionality within AFEMS / CERT / D200. 

Benefits
Enables the Air Force to migrate the equipment accounts from ILS-S to DPAS and sunset AFEMS.

Users
This impact all AF organizations.  Depending upon the design of this process, these processes could benefit other organizations who are looking for a system to  provide this functionality to manage their TDA Equipment purchases. 

Description
The Air Force is migrating its equipment mgmt functions that are performed within AFEMS / ILS-S to DPAS. One of those functions within AFEMS is the capability to create and maintain Allocation / Allowance Standards. These standards form the basis of what equipment and the amount each organization in the AF requires to perform its mission.  DPAS does not current provide this functionality that is required to sunset AFEMS.

Recommended
Incorporate an Allocation / Allowance process to DPAS that will systematically interact with DPAS's Authorization process.  It should be noted that Out Year data used to formulate the actual authorization for out years carries a Secret / Top Secret classification, thus some of the processes may required to be executed and maintained in a secure environment with only current information residing on the Non-Class side of DPAS. 

Mission Critical
Yes.  There is a requirement that is needed to replace the existing functionality within AFEMS. 

Benefits
Enables the Air Force to migrate the equipment accounts from ILS-S to DPAS and sunset AFEMS.

Users
This impact all AF organizations.  Depending upon the design of this process, these processes could benefit the USMC, and possibly other organizations who are looking for a system to  provide this functionality to manage their TDA Equipment. 

Description
Currently we have to forecast certain shelf life/service life items using individual memorandums and the expiration information showing on the DW01 is inaccurate and showing items as expired when they are not.  This is huge delay for forecasting and makes it impossible for leadership to track time change data. 

Recommended
We can extend the shelf life under inventory update manager, but we need the ability to extend the service life for items that have both.  When we extend the shelf life it doesn't change the overall expiration because the service life expiration currently can't be changed.  This makes it impossible to forecast and have accurate DW01s for our time change items that have extensions.  Please add the ability to extend service life, as show in the screenshot, under inventory update manager, re-identification.

Mission Critical
Critical, the system doesn't forecast correctly at this time, so the system isn't working for what it is intended to work.

Benefits
time savings and accurate data reporting.

Users
all

Description
The Air Force is migrating its equipment management functions that are performed within AFEMS / ILS-S to DPAS. One of those functions is the ability to communicate with CMOS transportation requirements for moving equipment among custodians and to DLA Disposition Services. DPAS needs to interface with CMOS for Asset Transfers and Asset Dispositions actions within the PA module as it does with the Warehouse module.

Recommended
Incorporate the use of CMOS within the Asset Transfer and Disposition processes for the movement of equipment. 

Mission Critical
Yes.  There is a requirement that is needed to replace the existing functionality within ILS-S that the AF user uses today to move equipment from Base to Base and to DLA Disposition Services. 

Benefits
Enables the Air Force to migrate the equipment accounts from ILS-S to DPAS and sunset AFEMS.

Users
This impact all AF organizations, and possibly other organizations that use CMOS as their TMO system.

Description
The Air Force is migrating its equipment management functions that are performed within AFEMS / ILS-S to DPAS. One of those functions is the ability to order equipment. The current Requisitioning capability within DPAS is limited orders being placed for a Warehouse.  The system should provide for the placement of an order for a Warehouse, a Property Equipment account record, and also provide for an order to be placed that is to be shipped to a Non-DPAS User.

Recommended
Modify the current Requisition process that resides within the Materiel Mgmt module to permit the placement of an order for PA, Warehouse, or a Non-DPAS User.  The process must be able to support Fund Targets by Quarter/Fiscal Year by Fund Code/ASN.

Mission Critical
Yes.  There is a requirement that is needed to replace the existing functionality within ILS-S that the AF user uses today to acquire the equipment they require to perform their mission. 

Benefits
Enables the Air Force to migrate the equipment accounts from ILS-S to DPAS and sunset AFEMS.

Users
This change could impact a large group of DPAS, both AF and other.

Description
The Air Force is migrating its equipment management functions that are performed within AFEMS to DPAS. One of those functions is the Small Arms / Light Weapons (SA/LW) Registry for the Air Force.  The DPAS does not currently have this functionality as part of its core system.

Recommended
Create the capability to communicate with Service Registries (Navy and Army) Transfers of SA/LWs (tracking of the Due In/Due Out), support for capturing SA/LW data for un-issued SAs and ancillary equipment located in warehouses, such as the Anniston Army Depot, providing registry reconciliation tools, along with the monthly reporting to the National SA/LW registry IAW with DLM 4000.25-2 and other DoD policies and procedures as it pertains to SA/LW.

Mission Critical
Yes.  There is a requirement to provide special handling / reporting for SA/LW.  This function must be subsumed by DPAS as AFEMS is sunset. 

Benefits
Enables the Air Force to sunset AFEMS, and provides benefits to the DPAS users who are currently reporting their SA/LW to the Navy Registry by automating the reporting of those weapons.

Users
All users who are involved with managing SA/LWs.

Description
The Air Force is migrating its management and accountability of its IT assets to DPAS.  As part of that effort, there is a requirement to identify and report the custodians of IT to the Air Force's AFWAY system.

Recommended
Create a Web Service Interface that will provide AFWAY with the data it requires.

Mission Critical
Yes.  This data is the only method that authorizes the IT Custodians to have visibility of IT orders in AFWAY.

Benefits
Providing information concerning the IT Custodians in DPAS to AFWAY will permit the IT Custodians to have visibility of IT orders within AFWAY.

Users
All Air Force IT Custodians

Description
Currently, there is no way to enforce Air Force DPAS M&U users to input Est Labor Hours on  Sub Work Orders when creating a Work Order. This is a mandatory function for user to input Est Labor Hours which leaders use for workload planning, scheduling maintenance and productivity assessments. This is also necessary so current information can be seen and sent to LIMS-EV, for leaders to view and use in vehicle maintenance production decision making processes. The failure of users not updating Est Labor Hours is preventing LIMS-EV from providing an accurate picture on workload productivity and Direct vs Est Labor Hour Variances. We propose making the Est Labor Hour data field a mandatory input when opening work orders in DPAS.

Recommended
The ability to ensure that all users are inputting Est Labor Hours in a Sub Work Order is crucial. When creating a Sub Work Order this field needs to be a mandatory and an error message needs to pop up when there is not a number in the Est Labor Hour field when no labor hours are entered.

Mission Critical
This is critical.  Enterprise Fleet managers count on viewing this information in order to make informed personnel decisions. This is mandatory for Mx Activities so the most current and accurate information is sent to the Enterprise Leadership view in LIMS-EV.

Benefits
This would benefit Air Force leadership by getting the most accurate and up to date maintenance status of all Air Force assets as well providing a viable performance indicator.

Users
This SCR will affect the entire AF vehicle site, all Air Force Fleet Managers/Superintendent and FM&A personnel utilize this information for day to day fleet management purposes.  

Description
Currently, the open work order dashboard displays all open work orders but does not provide enough information to quickly and accurately pull an Estimated Time In Completion (ETIC) report.

Recommended
Add available fields: LIN/TAMCN, Maint Grp ID, Equip Pool, Approval Date, Team, Remarks as well as a download feature (PDF & Excel) from the main open work order dashboard.  Also add filters on all column headers.  This will allow managers to sort the ETIC sheet as desired and print the information as it is displayed on the screen.  See attachment (below) which details basic requirement.

Mission Critical
Critical.  The current process does not give a Vehicle Fleet Manager the ability to look at the open work order screen and get an accurate depiction vehicle maintenance status of assets within the shop. 

Benefits
Benefits of this solution enable Vehicle Fleet Managers with the ability to check the status of their maintenance actions within a few clicks of the mouse.

Users
All Air Force Fleet Managers/Maintenance controllers and Material specialists utilize this information for day to day fleet management purposes.  

Description
The current design of the association of Master Issue List (MIL) to UIC requires 1 association record for every MIL-UIC combination, and does not allow the user to create a MIL that is available for every UIC in their Logistics Program regardless of the addition of future UICs.

Recommended
Create a checkbox on the Master Issue List Add/Edit screen that indicates this MIL is for all UICs.  Setup the screen such that if a user does select any UICs, it unchecks the box.  Set the database and code up such that no association records are required for MILs that have been set up to be available for all UICs.

Mission Critical
mission critical.  As more and more Master Issue Lists are created and associated to more UICs, the performance of that association will continue to degrade without this feature.

Benefits
Performance of the system.

Users
All users.

Description
Our current system allows attachments at the asset level however DPAS Warehouse only allows attachments at the Stock Number or Transaction level. The Proposed Improvement will allow us to create attachments at the ICN level and then migrate them over from eTIMS to DPAS.

Recommended
Allow Attachments at the ICN level through Inventory Update and During the Receiving Process for the following file types:

• jpeg,
• pjpeg,
• png,
• x-png,
• gif,
• pdf,
• MS Office (Word, Excel, Power Point)

Mission Critical
Mission Critical. Our warehouse is a central issue, shipping, and storage facility with owners and managers who are off site. Attaching files to an asset is crucial to communication and selection of the correct assets from locations across the globe.

Benefits
Allows us to successfully migrate from eTIMS to DPAS, Improves accuracy of data, shipments, and decisions for parties who are not in the same geographical location as the warehouse.

Users
All users can benefit from being able to attach records, pictures, files to an ICN.

26Jun2018 – cancelled per Randy Reed
This is the same as SCR 01126.

Description
Navy is undergoing FIAR audit.  Auditors are asking for the city and state be added to  asset universe reports to better define the actual physical address location of an asset.   Navy Major Commands and their subordinate UIC's are manually adding city and state to asset reports for reporting to the audit community which is a heavy lift burden.  Navy has a need to have City and State added to the Location table in order for CPO's and APO's to better account for and report asset physical address location for audit purposes. Navy needs a system wide solution instead of using a combination of manual workarounds. 

Recommended
Recommend City and State Fields be added to the Location Table and make these fields mandatory entries when adding or updating locations.   There maybe other solutions that are available that are not considered and Navy is willing to discuss those options. Also need City and State added as fields to the Inquiry/ Asset Management / Asset and Master Data/ Location modules for reporting purposes.

Mission Critical
Mandated. This SCR is a result of the DOD FIAR Audit efforts. Auditors are requiring BSO's to add City and State field to the Asset Universe Reports to identify actual physical address of the asset. 

Benefits
Adding these fields will add visibility of the actual physical address location of an asset relative to inventory and financial accountability.

Users
Would affect any users of the Property Accountability module DoD wide.

***

Per follow up communication from Boone with Navy PP&E/William Aldrich with Navy FMO, this is on hold/suspended temporarily pending further internal discussion between PP&E/FMO.  They intend to follow up by end of next week stating whether they want to amend the existing submission, or retract the existing SCR and resubmit something completely different down the line.

***

Description
The upcoming work report does not reflect the dates that are entered in the scheduled preventive maintenance screen. The scheduled maintenance that has the "last maint date" as the setting is showing on the report, but the "set schedule date" is not showing on the report.  In the past this report would show both dates and now it will only shows the one date. We would like this fixed so that we can properly report upcoming work orders to customers to properly project maintenance requirements. At this time we are using an additional spreadsheet to track information that DPAS should be reporting to us.

Recommended
That when a upcoming work report request is submitted that the report once received actually accurately reflects what is in the scheduled preventive maintenance schedule. That if a date change is made or a new schedule for is made for any equipment (new or existing) that that upcoming work report will update these changes within twenty four hours. This used to work.

Mission Critical
Critical accurate forecasting ensures customers know when they need to have equipment dropped off to be serviced (work order completed).  

Benefits
Keeps equipment maintenance up to date, reduces the possibility of equipment being out of compliance and possibly being deadlined, especially mission critical equipment such as forklifts, etc.

Users
I believe it probably affects all M&U concerned individuals

Description
Problem: Tracking utilization is very important in Fleet Management. The new Utilization Report Extract tracks and reports utilization, but needs to be updated for all assets loaded into DPAS. Currently, the report defaults the Util Target Monthly to 1000 for FAST Reportable vehicles and all FAST Reportable Vehicles Util Target Monthly isn't 1000. Also, the report defaults the Util Target Monthly to 0 for all other assets reporting utilization.

Recommended
When an Agency or Service is developing the DPAS catalog there are mandatory fields that are required to have data inputted; Yr SVC Life and Util SVC Life.
Each and every asset placed in DPAS must have a SN created, regardless of agency.
One agency may use 8yrs/200,000 and another 10yrs/250,000 (not saying either is right or wrong), but there must be values inputted. Everything is driven from these two fields.
  Using the two fields the calculation should be:

• Util SVC Life (250000)/Yr SVC Life (10)= Util Target Annual (25000)
• Util Target Annual (25000)/12 (months)=Util Target Monthly (2083)

The formula is agency neutral, it is the data in the fields that drive the end result.
This should be the case regardless of type of asset.
And that value should populate the Util Target Monthly in the MAM, as well as the report.
These values are already being utilized to develop the Utilization Report Extract.
Once the Util Target Monthly is calculated and populated request that it be greyed out for all users (this value will be calculated from the information gathered from the catalog), as well as the Minimum Objective Percent and Objective Percent.

Mission Critical
This is mission critical because it supports tracking proper use of assets and tracking of under utilized assets correctly.

Benefits
This will benefit all activities in DPAS by reducing time and error in reporting. Having DPAS perform the calculations allows the system to work for the user. It removes the human factor from having to perform calculations which can introduce errors.

Users
This should affect ALL users utilizing DPAS.