System lacks address options when generating a DD Forms1149, Requisition and Invoice/Shipping Document through Property Accountability (PA).  The form populates the "From" block using the assigned UIC's APO address.  In many circumstances, the item (i.e., vehicle) shipment location is not collocated with UIC's APO location.  The address issue results with the Transportation Office rejecting the shipment request because "From" block does not accurately reflect physical location of shipment.  Allowing DPAS users the ability to edit the "From" field generating the DD Form 1149 streamlines process, eliminates errors and provides accurate shipping documents.

 

 

Request DPAS add an editable "From" field to the Generate Forms > DD Form 1149 function similar to the "Ship To - Mark For" field.  Providing a space for users to manually enter the address and/or use the address browse function to populate Section 1 of the DD1149. Recommend linking the address browse function to addresses loaded under the UIC's Master Data within PA and Maintenance & Utilization (M&U) modules.  A dropdown menu allowing users to narrow Address Type search (i.e., EP-Equipment Pool, MO-Maintenance Officer, AO-Actbl Prop Officer, or 02-DODAAC TAC(2) used for FREIGHT).
The desired end result is the user generating a DD Form 1149 with their preferred "From" address vs. the system populating Section 1 with the UIC's APO address.

 

 

Critical.  Accurate shipping documents ensure warfighters receive critical items when and where necessary to execute mission.  Streamlining DPAS prevents erroneous shipment actions due to incorrect ship "From" location.  

 

 

Incorrect shipment documentation drives additional shipping costs, delays/cancels shipment and increases mission failure rates.  Adding address edit/selection function eliminates shortfalls and results in warfighter mission success.

 

This will affect all DPAS users.

AF has determined its contractor inventory control points (CICPs) also manage general support equipment for their program offices. The general support equipment in the possession of CICPs is a type of Government Furnished Equipment (GFE) and is currently not accounted for or financially reported on the AF financial statements.  AF GFM-A team proposes incorporating the additional ITFRs into the DPAS ICP and Warehouse modules to allow the CICPs to account for and financially report the GFE via the same processes in DPAS used for GFM.

 

 

Incorporate the additional ITFRs and process flows/narratives into the DPAS ICP and Warehouse modules.  Configure ICP module to capture key data elements including; Acquisition cost, Acquisition date and serial number; and calculate depreciation for capital assets. Configure ICP module to financially report capital assets with asset type code of “G” to GAFS-R.  

 

 

Asset accountability and financial reporting is mandated.  Need by date is Dec 2021.

 

 

This would provide accountability and financial reporting for AF GFE managed by contractors improving the AF’s audit results. This solution would replace the AF’s manual reporting efforts with automated processes using the AF’s Accountable Property System of Record (APSR) for Equipment.  Solution would benefit other services that use DPAS ICP and Warehouse modules for ICP accountability and financial reporting.

 

ALL AF GFM-A users of DPAS

 

DPAS does not allow for 18 characters for Job Order Number and Depreciation Job Order Number for the FAMIS-WCF interface - interface code "AC"

 

 

Update the FAMIS-WCF interface to allow 18 characters for Job Order Number and Depreciation Job Order Number due to DISA's OneFund implementation for interface code "AC"

 

 

Mission mandated - DISA's Working Capital Fund is moving to a single fund instead of two (combining TSEAS & CS). This change is going live on 10/1/21 for financial reporting and we need to update the interface from DPAS to properly account for PP&E.

 

 

This implementation is needed to correctly financial account for DISA's PP&E

 

Yes, this action affects all user within the Agency.

 

The DPAS current Property Accountability module does not provide for the Accountable Property Officer (APO) to request equipment from the Warehouse module to be issued, or purchased as would be customary when the DPAS Warehouse module is operating / provide the organization with its Base Supply functions.

 

 

The integration of the 2 modules will occur as a multiple phase approach.  This initial phase will enable the Warehouse (WM) to issue to the Accountable Property Office (PA) equipment that is on hand.  The system will establish a Due In record in the Property Accountability module at the Site/UIC with the Custodian being optional. Future phases will incorporate the ability for the APO to request items from the Warehouse establishing the Due In in PA and a Due Out in WM.  When the warehouse issues the item, the Due Out will be closed with the PA Due In being updated to reflect the item has been issued and is awaiting for the APO to receipt for the item.

 

 

This is part of the DPAS modernization effort that is to provide more cross integration of the modules / processes of DPAS.

 

 

This change will reduce the time required to receipt for materiel being issued from the warehouse to the property book as well as provide improved accuracy and financial accountability for the issued asset.

 

 

It will affect all organizations that are using the Warehouse and Property Accountability modules.

 

System does not provide Fuel Cd or Fuel Type Cd inquires or Reports at the asset level for complete vehicle fleet. Agency and Maint Activity users require information for higher headquarters or OSD data calls and to validate vehicle profiling accuracy within the Maint Asset Master.  System allows action for FAST reportable assets, but fails to allow complete vehicle fleet management.

 

 

Add Fuel Cd and Fuel Type Cd as available fields within Inquiries>Maintenance>Maint Asset.  Similar to FAST reportable assets, but for ALL assets

 

 

Critical and mandated.  Capability enables agency and vehicle fleet managers to fulfill Federal, DoD, and Air Force data calls similar to FAST and DLA-Energy reporting.  Data accuracy ensures compliance with Executive Orders and congressional mandates.

 

 

Available of fields significantly reduces time-to-need executing data calls and validating records. Current process requires accessing each asset's MAM to view the Details Basic Tab.  Another option is submitting a DPAS Tier II customer support request for data.  Both options increase task for time-sensitive data calls and records validation on information readily available for FAST assets, but lacking on complete vehicle fleet.  Adding inquiry and report fields eliminates workload on all parties.

 

This will affect all users within the Air Force and fleet managers across the DoD.  

 

Message that displays when hovering over the "Non-Mission Capable" checkbox on the "Current Preferences", "Other Preferences" screen doesn't adequately explain the purpose of the option.  Request a more clear description be added.

 

 

Change message displayed when hovering over the "Current Preferences", "Miscellaneous Preferences" checkbox from "Check to default NMC in Work Order" to "Check to default all new Work Orders to NMC status".

 

 

Not mission critical but will reduce confusion and allow smoother transition to M&U for new personnel.

 

 

Improves Work Order accuracy, reduces time spent opening new work orders. 

 

 

All M&U users.

 

DoD Serial Nbr field is not available as a field option in all M&U screens and functions.  USAF SE uses the DoD Serial Number field in M&U to associate the asset and DPAS record with the historical record in legacy systems.  We do this by documenting the legacy system ID in the DoD Serial Nbr field in DPAS.  Additionally, in many cases this ID is physically stenciled on the asset and is the primary means of ready identification.  

 

 

Include the DoD Serial Nbr as a field option on all inquiry screens.  Display DoD Serial Nbr field on all profiling, work order, work plan, maintenance schedule, and other primary functional screens where the serial number or asset ID are displayed.

 

 

Mission Critical.  For most AF SE maintenance organizations the DoD Serial Nbr represents the primary means of equipment identification when the equipment is in use.

 

 

Significantly reduces time spent identifying equipment when needed for maintenance or inspection, improves accuracy of documentation and accountability by providing the most used identification method on necessary screens.  Also has safety implications when a piece of equipment must be removed from service quickly to prevent injury to personnel or damage to a weapon system.  Also allows custodians to more quickly and accurately inventory equipment.  Significantly reduces time spent profiling by providing the most known and available identifier on the screen for assets awaiting profiling.

 

Affects all users.

 

 

 USMC has sunset the Technical Data Management System (TDMS), thus the TDMS interface is no longer operational.  

 

 

This SCR is to remove the TDMS Interface system from the DPAS.  As part of this effort, DPAS will remove / update the user's catalogs to reflect either FLIS or no external catalog that are currently aligned with TDMS.

 

 

Yes.  Unused code is not permitted to exist within a system (STIG violation).

 

 

Improves performance and reduces the cost of maintaining the system with all references and BRs associated with TDMS removed.

 

 

The TDMS interface was used by USMC entities.  The Consolidated Storage Program (CSP) has already re-aligned to utilize FLIS.  A few other catalogs are currently associated with the TDMS interface.

 

DPAS received a NFR for its 2021 SSAE 18 audit review for its review of system processes.  Currently DPAS's DAC, Quartz, and Pendulum processes provides no confirmation process when a DPAS administrator reviews background processes.  DPAS does produce a daily report relating to the DAC processes (Batch, Reports and Process Queue), but even within, DPAS does not have a documented process that indicates that DPAS has reviewed the report and has taken action when an action is required.  

 

 

DPAS develop a process where the System Administrator can confirm that a review of the processes was performed and the date/time it was performed.  The goal would be to have a single control that can be implemented throughout the system where the SA could select, and enter comments to confirm that a review was completed.  Upon Save, the process would write a row to a table containing the Users Id, Date/Time, what process was reviewed and the comments they may have entered.  When requested to show proof that the reviews were being conducted in accordance with the DPAS procedures, DPAS could export the data to provide validation that the review is being performed.

 

 

Yes - Satisfy the SSAE18 audit process, without having to save the page, convert it to PDF and digitally sign it every time a review is performed.  

 

 

Reduces the cost to validate the reviews are being performed and provides positive confirmation.  

 

 

This supports the SSAE 18 / MDS requirements for positive validation that DPAS is reviewing the system in accordance to its procedures.

 

Within the Issues - Unit Transfer section of the Warehouse Activity Report (LPWHR78), the
account name in which the assets are being transferred to is not displayed.

 

 

Add an additional column which contains the Account Name of who the assets were transferred to. If needed, the LIN/TAMCN or Condition Code can be removed from this section to provide the needed room of adding a new column.

 

 

Mandated - Day to day activities can still be completed.

 

 

Adding this additional column would assist in accountability as well as reduce the time as the user would have a report which shows the complete transaction of where the asset was transferred from and where it was transferred to.

 

This greatly affects our Armory users as they must be able to show the complete electronic transactions for accountability purposes. A minor affect is relayed to the rest of the user base for the times that a unit transfer is conducted.

 

Since the legacy handheld applications are no longer supported by the project, there is no method, outside of initial asset receiving to associate a UII marking or RFID tag information to assets within DPAS.

 

 

Provide the ability to capture and associate IUID markings and/or pRFID tag to an asset within DPAS utilizing AIT and/or mobile devices.  This include both serial and bulk pRFID tag information and would be available within the Property book and Warehouse modules.

 

 

There are more and more organizations evaluating passive RFID as a more effective method of asset identification.  There is also a need to collect and associate Bulk RFID tag information within DPAS to enable the conducting of physical inventories and performing issues.

 

 

Improves the accuracy and efficiency of identifying assets in several of the materiel management processes within DPAS

 

ALL

 

Update the DPAS Maintenance & Utilization CSS Style sheets to provide an updated look to the MU Module

 

 

Update the GUI to have a more modernized look

 

 

N/A

 

 

Improved customer experience for all DPAS users and consistency between DPAS modules

 

ALL

 

Update the DPAS Property Accountability module to provide relevant Asset data to the new Maintenance service.

 

Provide a list of all Assets for a given Stock Nbr when requested.

 

 

 N/A

 

 

Allow M&U to support both Stand-alone and PA/M&U Coupled customers using the same service.

 

ALL

 

DPAS Modernization SCR - DPAS will develop an enterprise Attachment Service to replace several existing attachment processes.  

 

 

Create an Attachment service that will have the capability to store, retrieve, and delete Attachments that can be used in all modules of DPAS.

 

 

Yes.  The attachment capability is an integral part of the DPAS application.

 

 

Streamlines the attachment process by having a single Attachment service for the application.

 

 

Yes.  It will replace the current attachment processes for all users.  

 

In Property Accountability, the newer "Stock Number Inquiry" (Inquiries - Catalog - Stock Number Inquiry) that was implemented with eCatalog functionality is missing a grid column option to select and add the Maintenance Group ID field value for inquiry searches/extract output that the legacy/original PA "Stock Number" labeled inquiry provides as a field option.  Navy needs to move to using the newer inquiry due to the nature of the old inquiry pulling additional catalog data from the old NSWC PA Site ID (NW-SWC) which still resides in Navy's PA agency hierarchy, but is tied to the JO-SOCOM catalog.  The newer "Stock Number Inquiry" is more efficient and does not appear to exhibit this behavior, but is missing the referenced and required grid column option being requested.

 

 

Add "Maint Group ID" selectable option (Grid Options - Columns) in the newer "Stock Number Inquiry" in Property Accountability.

 

 

Yes - Navy has a DPAS interface with external maintenance systems in our 4 Naval Shipyards.  Assets are added or removed from DPAS report to that interface daily. Thus, we need access to the Maint Grp ID field to review/identify all applicable stock numbers set to interface and those stock numbers that are set to interface for corrective action necessary to keep the DPAS assets reporting to the external maintenance programs at the shipyards.

 

 

Other organizations aside from Navy may benefit from the addition of this additional grid column option in the newer Stock Number Inquiry as well.

This would provide additional data to all users within our agency although a large, but limited number of personnel would require it.

 

Interface between DPAS-WM and MCPIC.  

 

 

Interface should accomplish the following:

 

Mission critical.  

 

 

Eliminates 'lost' containers due to moves not properly recorded in DPAS.  Improves inventory location accuracy.  

 

 

This affects USMC only, however the synergy between DPAS and MCPIC would be very useful to other services.  

 

System is depreciating Air Force CFO assets utilizing the old threshold standard for units with an acquisition cost of $100K or more with an acquisition date prior to November 2013

 

 

Modify systems internal algorithm to comply with $1M threshold retroactively as mandated by DoD 7000.14 Vol 4 Ch 25.

 

 

Mandated per DoD 7000.14-R Vol 4 Ch 25.

 

 

Needed to avert erroneous financial reporting

 

 

This change will affect all users within the Department of the Air Force (DAF)

 

PEO Missile & Space (M&S) has multiple warehouse and facility locations that support multiple programs.  Most programs have a some like items (Stock Nbrs). Given that there can be like items across programs, the current DPAS Commodity Security does not provide the access control that is required.  We need an option to restrict the actions of users to specific programs that are stored in the same warehouse.  Currently the Owning DoDAAC is used to identify the materiel owner / program within the warehouse.  

 

 

Given that that the Owning DoDAAC is currently used to identify the program/owner of the materiel, it logical that if DPAS were to control data access by Owning DoDAAC, this will provide the capability needed.

 

 

Given the sensitivity / pilfer-able nature of some of the items that PEO M&S has, this change is considered critical.

 

 

Implementing this type of data access will improve control of the materiel in the warehouse which will result in better data accuracy, which in turn will reduce the number of reconciliations resulting from warehouse workers personnel performing actions they are not otherwise authorized to perform.

 

 

This change is limited to warehouse operations.  Program restrictions will apply to a subset of warehouse personnel assigned to the warehouse.  Some warehouse personnel will have the authorization to work multiple programs.  

 

USSOCOM does not pass requisitions forward using ICP Module since USSOCOM is it's own Source Of Supply. USSOCOM takes contract information and manually builds all of the due-ins for the warehouses by using the Warehouse Module Receiving process. The PEO's of USSOCOM need their contractor Logistics Managers (LMA's) located at the SOFSA Warehouse to be able to perform the manual build of due -ins,  but not perform the remaining steps/processes of the Receiving Process (Receive, Verify, Accept). This is a separate responsibility from our contracted workforce that conducts receive and verify processes.  

 

 

Create a new role in Warehouse Module that limits the User Role to perform the Material Management Functions - LPWNH19 and LPWNH19D process in Receiving. This will enable a select group of contractors to build the due-ins for the warehouses as the PEO representative but block them from performing other receiving actions to maintain separation of duties

 

 

This is to streamline processes for the SOCOM PEO's that are responsible for inputting their purchase orders into DPAS as Due-Ins but have no means to do so.  

 

 

Benefit is this will improve accuracy and speed up the Receiving Process at the USSOCOM Warehouses. This change will allow due-ins to be be pre-built by the contract workforce identified by the PEO's. These PEO/Program LMA's will be focused on their contract data, and input that data into the Warehouse. This process improvement will free up personnel tasked with ICP management that are currently performing manual due-in builds

 

This impacts only USSOCOM Agency users since USSOCOM is it's own Source of Supply. Our only option currently is to manually build our Due-ins by leveraging people that should not be conducting those transactions.

 

DPAS M&U does not have a data field specifically for Corrosion Scores, Paint Stack-ups or the Date an item was Last Painted as mandated by service policy. The proposed improvement is adding these fields to the work order form. This will allow for documentation and historical record keeping of this required information at the enterprise level.

 

 

Add (to M&U) Four drop-down menus, one for Corrosion Scores (5 options), one for Primers, one for Topcoats, and one for Color. Adding a date selection box for Date Last Painted.

 

 

Recording of corrosion scores is mandated by Air Force Policy and this change would allow accurately documenting condition and enterprise wide viewing of those records, which is currently impossible.

 

 

This solution would allow for support equipment and vehicle flights to have all the information they need about equipment corrosion status to be accessible at the enterprise level. Having records of corrosion scores allows for prioritizing for corrosion maintenance and assessment of fleet corrosion health/readiness. Recording the coating records allows the flights to be prepared for coating refurbishment activities by ensuring they have the required coatings before tearing down the equipment. This also improves accountability and tracking as certain primers and coatings are currently being phased out. This allows for equipment with these coatings to be easily identified so that resources can be allocated for repainting.

 

 

ALL users - The benefits of having this capability would apply to every user of Support Equipment or Vehicles, especially any users documenting maintenance the equipment, including maintainers, fabrication flights, MAJCOM Corrosion and Fabrication Functional Managers, as well as personnel within AFLCMC/WNZ and AFLCMC/EZP-CPCO who are responsible for the SE&V, as well as any commanders needing to identify readiness issues.