IDTitleSCR NumberDPAS ModuleReporting OrganizationStateHistoryDescription
20620ASP.NET Session State01736PALeidosNewSubmitted 11/24/2021<p><b>Description:<br />During periods of high usage, in production, the SQL server session state database provider experiences intermittent locking and latch contention, which reduces overall system performance, stability and responsiveness.<br /></b></p> <p><b> </b></p> <p><b>Recommended:<br /></b></p> <p><b>Update the following environments to use the ASP.NET Session State with SQL Server In-Memory OLTP Database Session Provider<br /></b></p> <p><b> </b></p> <p><b>Mission Critical:<br /></b></p> <p><b>With the additional users being added to support Air Force Maintenance, this change is required<br /></b></p> <p><b> </b></p> <p><b>Benefits:<br />Reduced locking and latch contention resulting in better performance, stability and responsiveness.<br /></b></p> <p><b> </b></p> <p><b>Users:<br />Yes. All users could see an improvements with this change.<br /></b></p>
20619Automate Transfer of Phyical Inventory Data from Handheld to DPAS01735PALeidosNew <p><b>Description:<br /></b></p> <p><b>The DPAS Progressive Web App "PWA" for conducting a physical inventory was initially designed to be 100% off-line. To utilize, the user had to manually export and import the data using an Excel file created/managed by DPAS. There was no automated connection between DPAS and the PWA. DPAS needs to provide a seamless automated transfer of the physical inventory data without having to copy and paste files.<br /></b></p> <p><b> </b></p> <p><b>Recommended:<br />Provide the capability to for the user to establish an authenticated session between a mobile device and DPAS providing for transfer of the PI data between the device and DPAS without the need for export/import. Once the transfer is complete provide for the PI to be conducted without being connected to DPAS.<br /></b></p> <p><b> </b></p> <p><b>Mission Critical:<br />highly desire and requested<br /></b></p> <p><b> </b></p> <p><b>Benefits:<br />Reduces time and complexity for the user. Eliminates the need for the excel import/export process, and improves data accuracy / integrity, eliminating the need for a manually transferred data file<br /></b></p> <p><b> </b></p> <p><b>Users:<br />all inventory personnel responsible for conducting/reporting physical inventory counts<br /></b></p>
20618SCR_01734 - Customer Support Request01734EnterpriseLeidosNew <p><b><span lang="EN-CA">Description:<br />The current DPAS internal trouble reporting process is limited to users of the PA module. DPAS needs to provide the capability to all modules of DPAS. In addition to submitting issues, users should have inquiry and update capabilities of their tickets. If they erroneously create one, they should be able close it.<br /></span></b></p> <p><b><span lang="EN-CA"> </span></b></p> <p><b><span lang="EN-CA">Recommended:<br />Update the user interface to the current DPAS design. Modernize the back end services to the latest tech stack, establishing api endpoints within a service that will support the new user interface to enable it to be deployed to all modules. The initial efforts will be targeting the DPAS end user community. The M&U module is the initial module targeted for modernization, and will be the first module to have the new capabilities. Once it is operational within the M&U module, implementation will be to the other modules of DPAS. The Customer Support Center will continue to use its existing processes until the it has been implemented across all DPAS modules.<br /></span></b></p> <p><b><span lang="EN-CA"> </span></b></p> <p><b><span lang="EN-CA">Mission Critical:<br />This SCR is part of the DPAS Modernization effort. The submission / management of user initiated help tickets is to be implemented module independent. The overall effort is to reduce integration efforts as modules are added and to provide the user and customer support staff with improved capabilities.<br /></span></b></p> <p><b><span lang="EN-CA"> </span></b></p> <p><b><span lang="EN-CA">Benefits:<br />1. Improve User Experience. 2. Provide the user with the capability to review the status of their ticket without the need to contact the Customer Service Center 3. Provide the user with the capability to update the tick with additional information / close a ticket should they determine it was no longer an issue. 4. Streamline / Reduce the workload of the Customer Service Center.<br /></span></b></p> <p><b><span lang="EN-CA"> </span></b></p> <p><b><span lang="EN-CA">Users:<br />The capability will be provided to all DPAS users.<br /></span></b></p> <p><b><span lang="EN-CA"> </span></b></p>
20617Submit Materiel Mgmt Accounting Transactions to Advana01733EnterpriseUSAFNewSubmitted 11/08/2021<div> <p><b>Description:</b></p> <p><b>Advana is the DoD data store for financial feeder transactions. DPAS currently sends accounting transactions for the Property Accountability module, but is not sending accounting transactions that are generated from its Materiel Management. module. DPAS needs to transmit accounting transactions that are generated for the Air Force GFM-A OM&S activity to enable full accounting of all GAFS-R transactions.<br /><br /></b></p> <p><b> </b><b>Recommended:</b></p> <p><b>Incorporate the accounting transactions that are generated from within Materiel Management module along with the Property Accountability accounting transactions to Advana on a monthly basis as part of the UOT feed.<br /></b></p> <p><b> </b></p> <p><b>Mission Critical:<br />Yes. With Advana having all financial feeder transactions, it should include those generated by DPAS's Materiel Management module.<br /></b></p> <p><b> </b></p> <p><b>Benefits:<br />Provides full accounting of all DPAS accounting activity. Enables a reconciliation of all accounting transactions between the source and financial system.<br /></b></p> <p><b> </b></p> <b>Users:</b></div> <div><b>All customers requiring financial reporting for materiel/equipment held within the Materiel Management module.</b></div>
20616MEPS Manager Role for WM01732WarehouseUSMEPCOMNewSubmitted: 27 Oct 2021<div><b>Description:</b></div> <div> </div> <div>Need a customized role with access specified on the attached/referenced spreadsheet. The role is to be called "MEPS Manager" and have a curriculum number of 9024. </div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>Create customized role.</div> <div> </div> <div><b>Mission Critical:<br /></b></div> <div> </div> <div>No</div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div>Gives USMEPCOM users a limited access role for the processes needed for their direct function. Otherwise the next best role gives too much access to processes not needed or trained on.</div> <div> </div> <div><b>Users:</b></div> <div><b> </b></div> <div>Yes (Affects all users)</div>
20615User Queries For All Modules01731EnterpriseLeidosNewSubmitted: 18 Oct 2021<div><b>Description:</b></div> <div> </div> <div>DPAS does not currently provide users (to include Information Owners (IOs)) the ability to run user access/role queries in all modules.  The 'Agency Pre-defined Inquiry' role does provide limited queries for PA and M&U only; however, "User Training Status" and "Users UIC"  need to be improved to provide additional helpful user column information.  All other modules need a role to provide accurate and helpful user queries.  (note: query "User Listing" apart of Agency Pre-defined Inquiry role does not provide accurate user information).</div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>For PA/MU improve the Agency Pre-defined Inquiry role to include additional user column data.  For all other modules provide new role for user access/role query ability.</div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>Yes, this is mission critical to assist Commands with managing their user base as well as assist them in completing their Annual User Audit.  This also helps us to support our SSAE audit readiness.</div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div>Appropriate users (to include Information Owners and Alternates) will have the ability to run user queries in all modules to have visibility of their users' access and roles to support the needs of their user base as well as complete their Annual User Audits.</div> <div> </div> <div><b>Users:</b></div> <div><b> </b></div> <div>This affects all users who need the ability to run user access queries to support their command's access to DPAS.</div>
20614DD 1149 'From' Address Option01730EnterpriseVSCOSNewSubmitted: 14 Oct 2021<div><b>Description:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Recommended:<br /></b></div> <div> </div> <div>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).<br /> <div> </div> 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.</div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>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.  </div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Users:</b></div> <div><b> </b></div> <div>This will affect all DPAS users.</div>
20613Add GFE Accountability and Financial Reporting to ICP/WH Modules01729EnterpriseUSAFNewSubmitted: 23 Sept 2021<div><b>Description:</b></div> <div><b> </b></div> <div>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.</div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>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.  </div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>Asset accountability and financial reporting is mandated.  Need by date is Dec 2021.</div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Users:</b></div> <div><b> </b></div> <div>ALL AF GFM-A users of DPAS</div>
20612FAMIS-WCF Interface Update01728PADISANewSubmitted: 14 Sept 2021<div><b>Description:</b></div> <div> </div> <div>DPAS does not allow for 18 characters for Job Order Number and Depreciation Job Order Number for the FAMIS-WCF interface - interface code "AC"</div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>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"</div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div>This implementation is needed to correctly financial account for DISA's PP&E</div> <div> </div> <div><b>Users:</b></div> <div><b> </b></div> <div>Yes, this action affects all user within the Agency.</div>
20611WM Issue to PA01727EnterpriseLeidosNewSubmitted: 07 Sept 2021<div><b>Description:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>This is part of the DPAS modernization effort that is to provide more cross integration of the modules / processes of DPAS.</div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Users:</b></div> <div> </div> <div>It will affect all organizations that are using the Warehouse and Property Accountability modules.</div>
20610Fuel Cd - Fuel Type Cd Inquiry01726MUDF-VEHSNewSubmitted: 03 Sept 2021<div><b>Description:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>Add Fuel Cd and Fuel Type Cd as available fields within Inquiries>Maintenance>Maint Asset.  Similar to FAST reportable assets, but for ALL assets</div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Users:</b></div> <div><b> </b></div> <div>This will affect all users within the Air Force and fleet managers across the DoD.  </div>
20609Change Hover Note in M&U Preferences01725MUUSAFNewSubmitted: 02 Sept 2021<div><b>Description:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>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".</div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>Not mission critical but will reduce confusion and allow smoother transition to M&U for new personnel.</div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div>Improves Work Order accuracy, reduces time spent opening new work orders. </div> <div> </div> <div><b>Users:</b></div> <div> </div> <div>All M&U users.</div>
20608Adding DoD Serial Nbr to Field Options & MU Screens01724MUUSAFNewSubmitted: 02 Sept 2021<div><b>Description:</b></div> <div> </div> <div>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.  </div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Benefits:<br /></b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Users:</b></div> <div><b> </b></div> <div>Affects all users.</div> <div> </div>
20607TDMS Interface Removal01723EnterpriseLeidosNewSubmitted: 30 Aug 2021<div><b>Description:</b></div> <div> </div> <div> USMC has sunset the Technical Data Management System (TDMS), thus the TDMS interface is no longer operational.  </div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Mission Critical:<br /></b></div> <div> </div> <div>Yes.  Unused code is not permitted to exist within a system (STIG violation).</div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div>Improves performance and reduces the cost of maintaining the system with all references and BRs associated with TDMS removed.</div> <div> </div> <div><b>Users:</b></div> <div> </div> <div>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.</div>
20606DPAS System Admin Review Process01722EnterpriseLeidosNewSubmitted: 30 Aug 2021<div><b>Description:</b></div> <div> </div> <div>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.  </div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>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.  </div> <div> </div> <div><b>Benefits:<br /></b></div> <div> </div> <div>Reduces the cost to validate the reviews are being performed and provides positive confirmation.  </div> <div> </div> <div><b>Users:</b></div> <div> </div> <div>This supports the SSAE 18 / MDS requirements for positive validation that DPAS is reviewing the system in accordance to its procedures.</div>
20605Warehouse Activity Report01721WarehouseUSSOCOMNewSubmitted: 26 Aug 2021<div><b>Description:</b></div> <div> </div> <div>Within the Issues - Unit Transfer section of the Warehouse Activity Report (LPWHR78), the<br />account name in which the assets are being transferred to is not displayed.</div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>Mandated - Day to day activities can still be completed.</div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Users:</b></div> <div><b><br /></b>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.</div>
20604UII and pRFID Association01720EnterpriseLeidosNewSubmitted: 17 Aug 2021<div><b>Description:<br /></b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div>Improves the accuracy and efficiency of identifying assets in several of the materiel management processes within DPAS</div> <div> </div> <div><b>Users:</b></div> <div><b> </b></div> <div>ALL</div>
20603MU CSS Update01719MULeidosNewSubmitted: 16 Aug 2021<div><b>Description:</b></div> <div> </div> <div>Update the DPAS Maintenance & Utilization CSS Style sheets to provide an updated look to the MU Module</div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>Update the GUI to have a more modernized look</div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>N/A</div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div>Improved customer experience for all DPAS users and consistency between DPAS modules</div> <div> </div> <div><b>Users:</b></div> <div><b> </b></div> <div>ALL</div>
20602PA Asset Data Messages to M&U01718EnterpriseLeidosNewSubmitted: 12 Aug 2021<div><b>Description:<br /></b></div> <div> </div> <div>Update the DPAS Property Accountability module to provide relevant Asset data to the new Maintenance service.</div> <div><b> </b></div> <div><b>Recommended:</b></div> <div> </div> <div>Provide a list of all Assets for a given Stock Nbr when requested.<br /> <div>Provide single messages for Asset updates due to: Receipt; Transfer; Disposition; Update; Reversal.</div> </div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div> N/A</div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div>Allow M&U to support both Stand-alone and PA/M&U Coupled customers using the same service.</div> <div> </div> <div><b>Users:</b></div> <div><b> </b></div> <div>ALL</div>
20601Attachment Service01717EnterpriseLeidosNewSubmitted: 03 Aug 2021<div><b>Description:</b></div> <div> </div> <div>DPAS Modernization SCR - DPAS will develop an enterprise Attachment Service to replace several existing attachment processes.  </div> <div> </div> <div><b>Recommended:<br /></b></div> <div> </div> <div>Create an Attachment service that will have the capability to store, retrieve, and delete Attachments that can be used in all modules of DPAS.</div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>Yes.  The attachment capability is an integral part of the DPAS application.</div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div>Streamlines the attachment process by having a single Attachment service for the application.</div> <div> </div> <div><b>Users:</b></div> <div> </div> <div>Yes.  It will replace the current attachment processes for all users.  </div>
20600Maint Group ID Grid Column Option - Stock Number Inquiry01716PANAVSUPNewSubmitted: 30 Jul 2021<div><b>Description:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>Add "Maint Group ID" selectable option (Grid Options - Columns) in the newer "Stock Number Inquiry" in Property Accountability.</div> <div> </div> <div><b>Mission Critical:<br /></b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div>Other organizations aside from Navy may benefit from the addition of this additional grid column option in the newer Stock Number Inquiry as well.</div> <div><b> </b></div> <div><b>Users:</b></div> <div><b> </b></div> <div>This would provide additional data to all users within our agency although a large, but limited number of personnel would require it.</div>
20599DPAS - MCPIC Interface01715WarehouseUSMCNew29 Jul 2021<div><b>Description:</b></div> <div> </div> <div>Interface between DPAS-WM and MCPIC.  </div> <div> </div> <div><b>Recommended:<br /></b></div> <div> </div> <div>Interface should accomplish the following:<br /> <div>1.  Automated moves between MCPIC and DPAS-WM.  When MCPIC picks up a location change for an item, it converts it from GPS to a DPAS-WM location and then passes that new location to DPAS-WM.   DPAS-WM automatically does the move transaction to place the identified asset in the location identified by MCPIC.  </div> <div>2.  Tags can be printed in either system but it is recommended that MCPIC generate all pRFID tag numbers.   This is prevent identical numbers being generated using the the DoD 96 bit EPC structure.</div> <div>3.  MCPIC will pass information to DPAS in any format approved by DPAS PMO.  This will include direct data exchange, MILS, or DLMS.  </div> <div>4.  MCPIC will utilize asset data found in DPAS-WM Catalog when tagging assets in order to minimize any exception errors.  </div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>Mission critical.  </div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div>Eliminates 'lost' containers due to moves not properly recorded in DPAS.  Improves inventory location accuracy.  </div> <div> </div> <div><b>Users:</b></div> <div> </div> <div>This affects USMC only, however the synergy between DPAS and MCPIC would be very useful to other services.  </div>
20598CFO Threshold Change01714PAUSAFNew29 Jul 2021<div><b>Description:</b></div> <div> </div> <div>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</div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>Modify systems internal algorithm to comply with $1M threshold retroactively as mandated by DoD 7000.14 Vol 4 Ch 25.</div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>Mandated per DoD 7000.14-R Vol 4 Ch 25.</div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div>Needed to avert erroneous financial reporting</div> <div> </div> <div><b>Users:</b></div> <div> </div> <div>This change will affect all users within the Department of the Air Force (DAF)</div>
20597Data Access by Owning DoDAAC01713WarehouseArmy: ASA/ALTNewSubmitted: 12 Jul 2021<div><b>Description:</b></div> <div> </div> <div>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.  </div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Mission Critical:<br /></b></div> <div> </div> <div>Given the sensitivity / pilfer-able nature of some of the items that PEO M&S has, this change is considered critical.</div> <div> </div> <div><b>Benefits:<br /></b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Users:</b></div> <div> </div> <div>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.  </div>
20596Warehouse Receiving Due In Role01712WarehouseSOCOMDoneSubmitted: 01 Jul 2021<div><b>Description:</b></div> <div> </div> <div>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.  </div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>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</div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>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.  </div> <div> </div> <div><b>Benefits:<br /></b></div> <div> </div> <div>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</div> <div> </div> <div><b>Users:</b></div> <div><b> </b></div> <div>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.</div> <p><strong>Completed - Release 2021.2.3 - 23 July 2021</strong></p>
20595M&U Corrosion Score and Coating Fields for Work Order Forms01711MUUSAFNewSubmitted: 30 Jun 2021<div><b>Description:<br /></b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div>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.</div> <div> </div> <div><b>Users:</b></div> <div> </div> <div>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.</div>
20594ICP MRO Multiple Upload01710Materiel ManagementDLANewSubmitted: 28 Jun 2021<div><b>Description:</b></div> <div> </div> <div>Request a file upload function and template for the ICP (aka Materiel Management) in the Customer Requisition Process to mass upload multiple MROs (Customer Requisitions) in an excel spreadsheet.  Once uploaded, have the function in ICP module to validate each MRO qty and location (aka RSA) - currently exists and is the process to release each MRO to the Warehouse.</div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>Update DPAS logic to allow for mass MRO entry via a file upload. See above.  At this time, the following Data elements would be provided in the Mass Upload Template:  Ordered By (DoDAAC/RIC), Ship To (DoDAAC/RIC), Owning ICP (DoDAAC/RIC), Stock Number (aka LSN), Qty, RDD, Priority Designator, demand code, media status code, fund code, signal code, POC Name, POC Phone #...<br /> <div> </div> Any field that is currently available or required in ICP when creating an MRO request.</div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>No, but would significantly improve MRO process.</div> <div> </div> <div><b>Benefits:<br /></b></div> <div> </div> <div>Reduce the manpower to enter multiple MRO requests from external to DPAS</div> <div> </div> <div><b>Users:</b></div> <div><b> </b></div> <div>Yes (affects all users within Component/Agency)</div>
20593Warehouse User Listing01709WarehouseUSAF/DH-VEHSNewSubmitted: 25 Jun 2021<div><b>Description:</b></div> <div> </div> <div>Excessive time required requesting DPAS Warehouse access data from DPAS security.  </div> <div><b> </b></div> <div><b>Recommended:</b></div> <div> </div> <div>Propose system update allowing agency level users to generate inquiry for DPAS Warehouse UICs, User Roles, Access Level, Assigned Roles and Certified Training CBTs.  DPAS PA has similar inquiry and request same or similar function within Warehouse. Process will streamline and standardize inquiry for modules minimizing contact with DPAS security.  Additionally, update a searchable option for DoD ID number allowing easier filtering data mining.</div> <div><b> </b></div> <div><b>Mission Critical:</b></div> <div> </div> <div>Air Force Instruction 24-302, Vehicle Management requires accurate records on user level access into the Fleet Management Information System (FMIS).  Providing a streamlined and standardized inquiry for modules will meet requirement.</div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div>Process will streamline and standardize inquiry for modules minimizing contact with DPAS security.  Additionally, an updated searchable option for DoD ID number will allow easier filtering data mining.  Effort reduces touch point time from DPAS security and allows agency better accountability on trained personnel within DPAS.  Provides leadership accurate, accountable and timely responses to data inquiries vs. days waiting on an outside agency generating information and emailing results to requesting agency.</div> <div> </div> <div><b>Users: </b></div> <div><b> </b></div> <div>Yes, affects all users within warehouse.  </div>
20592Defaults of GFP Master Data01708PALeidosNewSubmitted: 17 Jun 2021<div><b>Description:</b></div> <div> </div> <div>Currently Users must take action to set up WAWF User ID, WAWF flag set to Yes for Contracting Loan Address and WAWF set to Yes for DODAAC to execute GFP file transactions to PIEE.</div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>On behalf of Joe Stossel and Daryl Hanchock change master data processes to default so that when an asset is placed on loan to contract all data is set up to execute the outbound file to PIEE.  </div> <div> </div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>Yes</div> <div> </div> <div> </div> <div><b>Benefits:</b></div> <div> </div> <div> Better reporting of GFP to PIEE</div> <div> </div> <div><b> </b></div> <div><b>Users:</b></div> <div> </div> <div>Yes (all users within Component/Agency) </div>
20591Data feed to SCORE01707PAAF: A4/HAF FH-AFHAFNewSubmitted: 11 Jun 2021<div><b>Description:</b><br />AF has manually tracked and recorded Controlled Cryptographic Items (CCI) device location/details on spreadsheets gathered from multiple systems. Request an automated report with specific data elements is sent to the HQ CCC centralized repository<br /><br /></div> <div><b>Recommended:</b><br />Push automated report to HQ CCC centralized repository on a recurring basis.<br /><br /></div> <div><b>Mission Critical:</b><br />IAW CNSSI 4001 the Departments are required to track and manage all COMSEC/CCI assets<br /><br /></div> <div><b>Benefits:</b><br />Reduces time for individuals to process and pull a report, improves accuracy and accountability<br /><br /></div> <div><b>Users:</b></div>
20590ICP Catalog Roles01706Materiel ManagementSOCOMNew04 Jun 2021<div><b>Description:</b></div> <div><b> </b></div> <div>With DPAS Release 2021.2, the ICP/Material Management Module gained the ability to perform cataloging functions across most of the existing ICP User Roles. This gives anyone with those roles the ability to change the catalog which impacts users across the SOCOM Enterprise. The new catalog capability in the ICP will negatively impact USSOCOM ability to maintain a cataloging standard across the SOCOM Enterprise.</div> <div> </div> <div><b>Recommended:</b></div> <div> </div> <div>Update all of the current ICP Roles to remove Catalog Menu/Functions. Change those roles to read-only access to the Catalog.  Add a New Cataloger Role with full access to the Catalog Stock Number, MFR Part Nbr, and LIN/TAMCN screens/menus.</div> <div> </div> <div><b>Mission Critical:</b></div> <div> </div> <div>Mission Critical - Without this new Cataloger Role, USSOCOM will not be able to enforce a catalog standard across the command. This will result in the same asset(s) getting cataloged in ways that will not stand up to audit scrutiny.</div> <div> </div> <div><b>Benefits:</b></div> <div><b> </b></div> <div>benefit is control of the catalog which will results in auditability. This also sets the catalog to a standard which allows DPAS system users to get to the new Enterprise Standard that will be leveraged as a result of DPAS TECH Refresh</div> <div> </div> <div><b>Users:</b></div> <div><b> </b></div> <div>This will impact all users within the USSOCOM since they are all users/consumers of our Catalog.</div>
20589DLMS 842 Functionality01705EnterpriseSOCOMNew04 Jun 2021<p><strong>Description:</strong></p> <p>For Supply Discrepancy (SD) reporting / review, the DPAS model relies on its customers to utilize WebSDR. This SCR requests DPAS add support for supply discrepancy management within DPAS eliminating the need to have logins / use WebSDR providing USSOCOM with a single platform to manage its logistic supply processes. DLM 4000.25 Volume 2, Chapter 17 provides the business rules for SDRs. Appendix 3 contains a list of the SD codes.<br /> <br /><strong>Recommended:</strong></p> <p>1. Modify DPAS to inbound the DLMS 842 A/W Supply Discrepancies / Followup transactions.<br />2. Provide a display of the supply discrepancies with the capability to review, reply, close, and print new, pending, and closed supply discrepancies within the Materiel Mgmt. module. The view must support the display of the reasons for the SDR. A single SDR can have as many as 3 discrepancies reported within a single SDR<br />3. The review and response should provide a text area to provide narrative to the response, and document attachment support.<br />4. The Search Criteria area should include: Document Nbr, Date Range, Status, Stock Nbr, Originator (RIC/DODAAC) as a minimum. <br />5. Provide the capability to outbound DLMS 842 A/R responses<br />6. The MM dashboard should show counts of open Supply Discrepancies by categories (New, 0-7 days, 8-14 days, 15-21 days, >21 days) providing the user with a quick link to those categories of SDRs.<br /> <br /><strong>Mission Critical:</strong></p> <p>Yes. USSOCOM requires a single logistics view of its supply actions within DPAS which includes supply discrepancies.<br /> <br /><strong>Benefits:</strong></p> <p>Providing DPAS customers with support for supply discrepancies will reduce the cost and time to manage / resolve them, thus providing the warfighter with a more responsive resolution to their SDRs<br /> <br /><strong>Users:</strong></p> <p>This change affects customers/users who operate the Materiel Mgmt module and receive supply discrepancies to action.</p>
20588Feed Asset Data to Advana01704EnterpriseDLANewSubmitted: 27 May 2021<div><strong>Description:</strong> <br />OSD Comptroller has developed a data warehouse, initially to capture all transactions that are being sent to a financial system by feeder systems.  DPAS is currently sending monthly the fixed asset accounting transactions.  This SCR is to expand what DPAS is sending to include all assets in DPAS for all agencies.</div> <div> </div> <div><strong>Recommended:</strong> <br />Provide Advana the standard DPAS asset extract for all agencies.</div> <div> </div> <div><strong>Mission Critical:</strong> <br />The DPAS PM has directed this action at the request of OSD.  It is expected that Maintenance data will be the next set of data to be sent the Advana data warehouse.</div> <div> </div> <div><strong>Benefits:</strong> <br />OSD / components requiring this data can obtain that data from Advana</div> <div> </div> <div><strong>Users:</strong> <br /><br /></div>
20587Send Accounting Transactions generated from the DPAS Materiel Mgmt to Advana01703EnterpriseDLANewSubmitted: 27 May 2021<div><strong>Description:</strong> <br />DPAS is currently sending fixed asset accounting transactions to Advana monthly.  This data feed is currently limited to those transactions that are generated for assets/materiel held within the Property Accountability module of DPAS.  This SCR is to expand the accounting transactions to include those generated from within the Materiel Mgmt. module for assets/materiel held within warehouses (internal and external).</div> <div> </div> <div><strong>Recommended:</strong> <br />Provide Advana accounting transactions generated from within the Materiel Mgmt. module of DPAS.  If these transactions are sent in a separate file from the PA transactions, the file should contain a trailer record denoting the number of transactions the file contains. </div> <div> </div> <div><strong>Mission Critical:</strong> <br />All accounting transactions that are sent by feeder system to an accounting system are to be sent to Advana.</div> <div> </div> <div><strong>Benefits:</strong> <br />OSD / components requiring this data can obtain that data from Advana</div> <div> </div> <div><strong>Users:</strong> <br />This SCR will not impact the DPAS user community. This change will provide personnel reviewing / reconciling accounting feeder system data with what the accounting systems is receiving / processes.  It may reduce data calls from the DPAS user community</div>
20586Add "Trailer" record to UOT File being sent to Advana01702EnterpriseDLANewSubmitted: 27 May 2021<div><strong>Description:</strong> </div> <div>DPAS is currently sending fixed asset accounting transactions to Advana monthly.  The file does not contain a trailer record to denote the number of transactions contained within the file. Advana is requesting a trailer record be added to the file that would contain the number of records contained within the file.</div> <div> </div> <div><strong>Recommended:</strong> <br />Add a trailer record to the UOT file that identifies the number of accounting transactions contained within the file.</div> <div> </div> <div><strong>Mission Critical:</strong> <br />This change has been requested by Advana as a way to validate that they are receiving and processing all feeder system accounting transactions.</div> <div> </div> <div><strong>Benefits:</strong> <br />Ensures Advana receives and processes a complete file.</div> <div> </div> <div><strong>Users:</strong> <br />This SCR will not impact the DPAS user community. This change enhances / improves the reliability that Advana has all of the accounting transactions they were to receive from its feeder systems.</div>
20585IGC Interface of Air Force Assets01701PAAF: A4/HAF FH-AFHAFNewSubmitted: 26 May 2021<p><strong>Description</strong> <br /> The IGC program is a partnership between the U.S. Transportation Command and the Defense Logistics Agency. USTRANSCOM's Global Transportation Network (GTN) and DLA's Enterprise Business System have "converged" to provide DOD with an integrated set of networked, end-to-end visibility, deployment, and distribution capabilities.  Prior the Air Force sunset of their APSR AFEMS, AFEMS fed the IGC.  With their transition to DPAS, it was not known if there was a requirement to continue the interface of Air Force equipment in the custody of their users.  Recently, the IGC requested the Air Force restore this interface.  This SCR is to provide the IGC with the Air Force equipment that resides within the DPAS. </p> <p><strong>Recommended</strong> <br /> Provide the IGC with data feed of Air Force items in DPAS using the DPAS standard agency asset extract as tasked by the DPAS PM.  The extract is to execute weekly as an overlay.</p> <p><strong>Mission Critical</strong> <br /> This feed is considered mandated by the IGC with the Air Force concurring with the feed of their asset information.  The Air Force POC is Greg McCoy, Air Force HAF  AF A4LR.  Email: gregory.mccoy.6@us.af.mil</p> <p><strong>Benefits</strong> <br /> Improves visibility of assets for the Department for those users of the IGC.</p> <p><strong>Users</strong> <br /> This change will likely not affect any user of DPAS.</p>
20584Implement DLMS ADC 1400 - Reporting Inventory Cost Changes via DLMS 947I01700Materiel ManagementLeidosNewSubmitted: 24 May 2021<p><strong>Description</strong> <br /> DLMS ADC 1400 provides CICPs to report a missing cost element e.g. Updated MAC, or LAC via the DLMS 947I.  When materiel is received by a CICP, often times then Latest Actual Cost is not known due to the item having to go through their accounting system to have contract approved overhead costing applied.  This change is to provide the CICP a method for reporting the LAC post the applying of the overhead and other costs that may not be known at the time of the receipt, updated MAC and the item's Standard Price, as needed. This ADC also contains an administrative change for the DLMS 527R receipt that should be reviewed for possible changes to the DPAS user documentation.</p> <p><strong>Recommended</strong> <br /> With DPAS currently support the Air Force CICP programs for financial reporting of the inventory held by the contractor, DPAS will need to be modified to use the updated LAC / revised MAC in its valuation of the inventory and financial reporting of the inventory.  Upon receipt of the 947I, DPAS will need to review and make the necessary valuation adjustment as needed.</p> <p><strong>Mission Critical</strong> <br /> Yes - This SCR requires implementation to accurately report the financial value of the inventory held by the contractor.  This SCR is being submitted to implement DLMS ADC 1400.</p> <p><strong>Benefits</strong> <br /> The benefits of this SCR is the improved accuracy in the financial reporting of the cost of goods managed by a CICP contractor.</p> <p><strong>Users</strong> <br /> All components using DPAS to financially account for inventory in the custody of a CICP.</p>
20583Add Support for USSGL 199501699Materiel ManagementLeidosNewSubmitted: 05 May 2021<p><strong>Description</strong> <br /> U.S Treasury TFM USSGL Chart of Accounts implemented USSGL 1995 (General Property, Plant, and Equipment Permanently Removed but Not Yet Disposed).  It is also covered in : Accounting for the Disposal of General Property, Plant and Equipment from FFATR, No. 14. DPAS needs to add support for this USSGL.</p> <p><strong>Recommended</strong> <br /> Incorporate USSGL 1995 within the DPAS Chart of Accounts as part of the DPAS Modernization effort.</p> <p><strong>Mission Critical</strong> <br /> Yes. DPAS must be compliant with U.S Treasury Chart of Accounts</p> <p><strong>Benefits</strong> <br /> Financial Compliance</p> <p><strong>Users</strong> <br /> Yes.  Used for equipment that is no longer of need to the component / agency</p>
20582Global - Update / Configure Text at the end of DPAS Forms01698WarehouseLeidosNewSubmitted: May 4, 2021<p><strong>Description</strong> <br /> Allow LPs the ability to configure the text that displays at the bottom of Warehouse forms (Issue and Return receipts). Currently, the Issue and Return forms display text specific to being held to USMC judicial system if the member is required to pay back any prices for the issued items. This request came in as a old Help Desk ticket (31739) from the DISA LP but should consider this for the tech refresh in the Warehouse Module as we bring more and more on board to use the issue and return processes.</p> <p><strong>Recommended</strong> <br /> Allow users to configure the texts that display at the bottom of the Issue and Return receipts based on what the LP would like to see displayed to their users.</p> <p><strong>Mission Critical</strong> <br /> N/A</p> <p><strong>Benefits</strong> <br /> Benefits non-USMC elements using Warehouse.</p> <p><strong>Users</strong> <br /> All</p>
20581Allow Mass Update for Picks00963WarehouseUSMC: DMCRemovedSubmitted: 01/11/2016<p><strong>Description</strong> <br /> In the current version of DPAS, 3.2.01, the system only allows Picks that are being planned and conducted one at a time.  Currently, users are utilizing offline processes and applications (i.e., Excel) to physically conduct multiple Picks at the same time.  These offline processes are necessary when the Picks have the same “To” and “From” location.   To complete the process, users must compile several Pick numbers on a spreadsheet and email the spreadsheet to warehouse personnel to move assets concurrently instead of making the same trip multiple times.  DPAS users then have to update DPAS' Picks one at a time to confirm that the system reflects the changes that have occurred.  Users need the capability for a “mass update” process to Plan and Pick all affected Picks at one time.</p> <p><strong>Recommended</strong> <br /> It is recommended that in all Pick planning and conducting areas of the DPAS Warehouse Module, a “mass update” functionality be available.  This would include adding a checkbox before the Plan/Pick button on the Materiel Mgmt > Materiel Movement > Pick/Plan screens & Materiel Mgmt > Transportation > Pick/Plans screens.  This functionality shall work similar to the 'Take Selected' feature in the Inventory Master Selector that is utilized when picking assets for a single Pick Number. The user would be able to view the details of the Stock Number Picks and Inventory Picks of all previously selected Pick Numbers on the Plan Details and Pick Details page.  At this point, the user should have the ability to update and Pick all Picks simultaneously.</p> <p><strong>Mission Critical</strong> <br /> This is mission critical due to the fact that the current practices are cumbersome and unnecessarily lengthy.</p> <p><strong>Benefits</strong> <br /> If a “mass update” functionality is made available, this enhancement will dramatically increase the movement and flow of production.</p> <p><strong>Users</strong> <br /> This affects all users due to the direct, secondary, and exponential implications of Production.</p> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20580UIF Return Exchange00952WarehouseUSMC: CSPRemovedSubmitted: 22-Jan-2016<p><strong>Description</strong> <br /> Currently, there is no ability to do an exchange for Unit Issues. This function is available for Individual Issues and needs to be available for unit issues in order to exchange wrong gear or sizes without doing a complete return. </p> <p><strong>Recommended</strong> <br /> Recommending to add an exchange feature in Unit return that is similar to the Individual issue function.  </p> <p><strong>Mission Critical</strong> <br /> This will enable UIF's to do exchanges without having to complete full returns. </p> <p><strong>Benefits</strong> <br /> This will significantly reduce the time it takes to do an exchange. </p> <p><strong>Users</strong> <br /> All UIF</p> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20579Back Order Notification00949WarehouseUSMC: CSPRemovedSubmitted: 6/1/2015<p><strong>Description</strong> <br /> Currently, when a Warehouse Transfer is completed from an issue facility (ex. NCR IIF) to a different warehouse (ex. NCR DC) for an item that is not on hand at that warehouse there is no back order notice being created for the requesting warehouse. This means the requesting warehouse has no notification that there request will not be filled.</p> <p><strong>Recommended</strong> <br /> Recommending to add function that notifies the requesting warehouse that the item that they are requesting from a different warehouse wont be filled until that warehouse has the items to fulfill the request. </p> <p><strong>Mission Critical</strong> <br /> This will help notify the requesting warehouse that they will not receive items because the warehouse they are requesting from has no items on hand.</p> <p><strong>Benefits</strong> <br /> This will increase warehouse visibility of incoming warehouse transfers.</p> <p><strong>Users</strong> <br /> All IIF & UIF</p> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20578Serial Number Suspense File00946WarehouseUSMC: CSPRemovedSubmitted: 8/3/2015<p><strong>Description:</strong> <br /> Currently, when a user returns a serialized item other than their own (i.e. what was issued to them), their original serial number on the members record disappears and has no way of being tracked.</p> <p><strong>Recommended:</strong> <br /> Recommend adding a Serialized Suspense File to keep track of serial numbers that have not been returned. When a member returns a serial number other than their own issued serial number the system should automatically move that serial number into a serialized suspense file. This file should be placed in the "Inquiries" tab and should have all the same search-able parameters that "stock  number inventory" has.</p> <p><strong>Mission Critical:</strong> <br /> Yes.  This will help keep track of all serialized items, regardless of who turned in.</p> <p><strong>Benefits:</strong> <br /> This will increase visibility of all serialized assets.</p> <p><strong>Users:</strong> <br /> All IIF & UIF functions.</p> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20577Quality Inspection Report Form00943WarehouseUSMC: DMCRemovedSubmitted: 1/4/2016<p><strong>Description:</strong> <br /> In DPAS version 3.2, when maintenance is completed on an asset, a Quality Control (QC) Inspection Form is created and sent to QC.  The current QC Inspection Form does not have a dedicated space to enter what maintenance was conducted on the asset.  This creates a work stoppage for QC personnel since they must then use an off-line process to find out what maintenance was conducted along with what should have been inspected. The first page has excess space and the second page has a relatively small amount of data.  A necessary revision of this form should expand current data fields while incorporating additional areas necessary to fully execute the form.  This will enable all information, including an additional field for listing the maintenance conducted, to be captured and printed on a single piece of paper.</p> <p><strong>Recommended: </strong> <br /> It is recommended that Leidos add an additional field titled 'Required Maintenance' on the QC Inspection Form for the maintenance team to describe the maintenance conducted.  It is also recommended that Leidos reformat the current form in order to align all fields to fit on a single page.  A Microsoft Word document is attached that shows the current layout and the envisioned format that should optimize the functionality of this form.</p> <p><strong>Mission Critical:</strong> <br /> This is mission critical since the lack of information impedes work flow in QC.</p> <p><strong>Benefits:</strong> <br /> Revising this form will streamline the processes necessary for QC to complete an inspection report.  This change will also be beneficial by reducing the time to complete this task which consequently reduces direct labor cost and additionally decreases use of office supplies. </p> <p><strong>Users:</strong> <br /> This affects all QC inspectors.</p> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20576Project Code BOM Print00920WarehouseUSMC: DMCRemovedSubmitted: 9/24/2015<p>In Project Management, after entering Project Code (Screen Shot 1) and selecting Search, View Plan populates on the Grid Line (Screen Shot 2 ); then View Project Plan populates with Plan Selection Criteria and Bill of Materials (BOM) (Screen Shot 3). However, there is no capability to print or save the View Project Plan page. </p> <div> </div> <div>Recommended solution: User should have the option to print and/or save the View Project Plan page with BOM listed. </div> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20575Reversal capability in DPAS for inventory loss and gains00919WarehouseUSMC: DMCRemovedSubmitted: 9/24/2015<div>Problem:  The users need the ability to submit a reversal transactions on any 947I (D8 or D9) transactions which are erroneously submitted into the DPAS system.  DOD policy directs all systems to possess the capability to reverse out transactions erroneously submitted in order to correctly align inventory to the authorized transactions submissions.  Transactions (D9*/D8*) are being submitted incorrectly into the DPAS production system which should have been receipt due to high training curve.  Stock Control System (SCS) is designed to accept 947I (D8 or D9) transactions reversal intended to correct erroneous entries.</div> <div> </div> <div>Recommended solution: Provide the capability to reverse out transactions erroneously submitted in order to correctly align inventory to the authorized transactions submissions.  </div> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20574Implement Project Codes into ICP00908WarehouseUSMC: DMCRemovedSubmitted: 9/1/2015<div>There is no project type that supports the DMC Inventory Control Point (ICP) project. ICP projects assign Project Codes to specific pieces of inventory which are sent by and received for the ICP. Each project has a List of Requirements (LOR) which defines the Stock Nbrs or Part Nbrs which are acceptable to be received against the specified Project Code. All the items listed on a specific LOR are correlated in that they are all components of the same primary end item (PEI). </div> <div> </div> <div>Recommended solution: Create an ICP project type which will allow for the upload of the LOR, the assignment of a Project Code, as well as a way to record the PEI for which the items on the LOR are components for. Allow for the ability to record a POC for the project. Modify the receiving process to allow for the selection of an open ICP project and to also validate the Stock Nbr (or Part Number) as being valid against the LOR. Receiving should prevent the receipt of a Stock Nbr which is not listed on the LOR. </div> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20573Return Condition Codes00906WarehouseUSMC: CSPRemovedSubmitted: 8/28/2015<p>When doing a return for an UnManaged Bulk Kit, if an item of the kit is reported missing and or unserviceable the Condition Code should update in the Return to "G" thus, making this kit incomplete.   </p> <div> </div> <div>Recommended solution: Recommend that when doing a Return for an UnManaged bulk kit that the Condition code defaults to "G" when a piece of the kit is missing and or unserviceable.  This functionality was in production prior to 3.0.    </div> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20572Items Per Page00905WarehouseUSMC: CSPRemovedSubmitted: 8/28/2015<div>Currently we are only able to view 50 Items per page when most Issue and Returns are over 70 items per page creating the user to have to click between two screens. This causes issues of missing an item that was not marked during the Return or Issue and having to go back through both screens to find the problem.  </div> <div> </div> <div>Recommended solution: Recommend the Items per page be increased to 100 (Set PageMax = 100). This will help keep the error's down due to the fact the user would only have to view one screen thus saving time during an Issue and Return.    </div> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20571Suspense File/Queue & Server-side Error Processing for mobile transactions00852WarehouseUSMC: CSPRemovedSubmitted: 6/2/2015<div>A common problem on the DPAS Hand Held is that transactions processed receive an error (for various reasons).  When an error is received on the hand held, there is no capability to work the discrepancy.  There is also no capability on the hand held to clear the discrepancy, without going into the SD card on the device and deleting the .SDF file. </div> <div> </div> <div>Recommended solution: It is recommended that the DPAS Scanner pass all transactions to the DPAS On-Line application and push error transactions to an inbound error que that can be worked by system clerks.  The Scanner itself should push all work, regardless of error to this file for resolution.  Error files should not be stuck on the scanner with no capability to remove them without deleting the SDF file. The end state is that all work that is completed on a scanner be pushed to the warehouse for disposition, so that the warehouseman can continue work uninterrupted by errors. </div> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20570Generate a movement request when work order is updated with a state of ATWR00844WarehouseUSMC: DMCRemovedSubmitted: 5/27/2015<div>A Maintenance Movement Request should be system generated when a Work Order is updated with a Work Order State Cd of “AWTR- Approved-Awtng Transportation” and a new “Maint Loc” </div> <div> </div> <div> Current process requires 9 steps per move request to ensure AWTR has been generated. These 9 steps takes an average of 5 minutes per move request, currently DMC averages 50 move requests per day. An system-generated Maintenance Movement Request would save approximately 250 minutes per day. There also should be an Open Action Folder and Completed Transportation Folder generated in the main menu to be able to track the process of the AWTR. There should be an Open Action Folder created for Work Orders with the WO State Cd of “AWTR- Approved-Awtng Transportation” and a second Open Action Folder for these Work Orders once the asset has been moved to the requested Maint Loc. These folders would give the Maintenance Officers and assigned Primary Techs visibility of the current state of particular WOs and when service can be started on asset.</div> <div> </div> <div>Recommended solution: Maintenance Movement Request should be system-generated. A Maintenance Movement Request should be system generated when a Work Order is updated with a Work Order State Cd of “AWTR- Approved-Awtng Transportation” and a new “Maint Loc”.</div> <div> <div>Maintenance Movement Request is system generated when a Work Order is updated with a Work Order State Cd of “AWTR- Approved-Awtng Transportation” and a new “Maint Loc”.</div> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p> </div>
20569Required Delivery Date not reflected on M&U Work Order00816WarehouseUSMC: DMCRemovedSubmitted: 4/9/2015<div>The Required Delivery Date (RDD) from a MRO is not reflected on the M&U Work Order.  This is very important information when dealing with a shipment (MRO).</div> <div> </div> <div>Recommended solution: The Required Delivery Date (RDD) that a MRO is assigned in the WM Module has to carry over to the M&U Work Order.  As it is currently, the RDD shown in M&U is based off of the priority code assigned by the system and can be changed by any M&U User.  MROs are the top priority in Maintenance and their urgency is driven by the RDD on the MRO.</div> <div> <p>The Required Delivery Date (RDD) assigned in the WM Module has to be reflected on the M&U Work Order.</p> <p> </p> <p>Currently DMC needs a way to manage priority of WO opened from the Warehouse MRO process.  SCR is to have the RDD populate into the WO process and appear on the physical PDF of Work Order.  The need to prioritize WO coming from the Warehouse MRO process is a need across DOD.  In addition to RDD a better system method to manage this business process would be to have the MRO priority FAD relate directly to a WO Priority (Fred Maley).  Spoke with Rick M. 1 Dec 2016 of need of SCR.  Will work with development to have effort assigned. </p> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p> </div>
20568Quality Control Inspection - DW Form QIR Defect00804WarehouseUSMC: DMCRemovedSubmitted: 6/1/2015<div>In Materiel Management, Quality Control, customer needs the capability to fill out form DW 15 in quick and efficient manner.</div> <div> </div> <div>Recommended solution: Recommend the form be saved as a modifiable form giving the user the capability to edit and save the form.</div> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20567Quality Control Inspection - Search Criteria Request00799WarehouseUSMC: DMCRemovedSubmitted: 3/26/2015<div>In Materiel Management, Quality Control, customer needs the capability to track Quality Control actions with the same QC Request Number before and after it returns from M&U.</div> <div> </div> <div>Recommended solution: Recommend linking the same QC Request Number to the M&U Work Order Number throughout the process so that all transactions concerning the asset can be associated. The QC Number should be the same with a different QC type.</div> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20566Quality Control Inspection - Move Serial number to Main Grid Line00795WarehouseUSMC: DMCRemovedSubmitted: 6/1/2015<p>In Materiel Management, Quality Control, customer request the serial number be placed on the Main Grid line.</p> <div> </div> <div>Recommended solution:</div> <div> </div> <div>Recommend moving the Serial number from the secondary grid Line to the Main Grid so that it can be used as searchable field.</div> <div> </div> <div><span style="font-weight: bold;">NOTE: THIS IS DUE TO THE SERIAL NBR BEING ASSOCIATED TO THE SUB GRID DETAILS - NOT THE HEADER.  MULTIPLE SERIAL NBRS COULD BE ASSOCIATED TO THE HEADER.  However it could perhaps be made a Search Box Field....per TFS 12588 OR could do this like Associated Stock Nbrs in the Phys Inv process ???</span></div> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20565SKO Kits - additional data on packing list00718WarehouseUSMC: DMCRemovedSubmitted: 12/4/2014<div>When processing SKOs, the packing list does not contain the serial number, processors name or document number. Packing list should display serial numbers, processors name and document number.</div> <div> </div> <div>Create field on Packing list to place serial numbers, processors name and document number.</div> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20564M&U - mandatory unavailable days fields00707WarehouseUSMC: DMCRemovedSubmitted: 11/26/2014<p>Unavailable Service Days and Unavailable Maintenance Days are mandatory fields and do not pertain to our business. The user has to input a number in each of the two fields that has no meaning.</p> <div> </div> <div>Unavailable Service Days and Unavailable Maintenance Days are mandatory fields and do not pertain to our business. The user has to input a number in each of the two fields that has no meaning.</div> <div> </div> <div>Joe Stossel comment, 8/10/2015 - this is from the USMC DMC.</div> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20563M&U - apprvl, service end/start dates not mandatory00706WarehouseUSMC: DMCRemovedSubmitted: 11/26/2014<p>Once a tech has been assigned to a Work Order, a Service Start Date has to be entered. Without automation, the M&U supervisor must print W/O to give to assigned tech. At the time of printing W/O, the tech has not started the service yet making this date inaccurate.</p> <div> </div> <div>Approval Date (Date that supervisor initializes the W/O process), Service Start Date (Date that tech actually starts service) and Service End Date (Date that tech actually completes service) are three important date fields but do not need to be prepopulated or linked to priority code or anything else. They should be standalone date fields. Because there is no AUTOMATION in the M&U Module, a hard copy of each W/O must be printed and given to the assigned tech. The tech will have to write in his start and end dates on the printed copy. The supervisor will then have to reopen W/O and enter this information. This is the only way to capture somewhat accurate times for accountability and time management purposes without automation.</div> <div> </div> <div>Joe Stossel comment, 8/10/2015 - work with 680 and 684.</div> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20562Provide the ability to set and assign QC request00699WarehouseUSMC: DMCRemovedSubmitted: 11/24/2014<div>Within Materiel Management Receiving, there is no option to send to M&U within the acceptance screen of receipts.</div> <div> </div> <div>Should have a check box to send to M&U and selection drop down to identify required action. Also need an option to add remarks. This would prevent unnecessarily sending a document to QC only to have it assigned and sent back to the same inspector for inspection.</div> <div> </div> <div>Possibly:  Add to any process that generates QC requests … </div> <div> </div> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20561Manual Close Intransits by Document Nbr01697Registry (SA/LW)LeidosNewSubmitted: 4/26/2021<p><strong>Description</strong> <br /> The registry manages SA/LW by Stock Nbr / Serial Nbr.  A single shipment may include many items. The requirement to close each intransit singularly is time consuming.  USSOCOM, a user of the DPAS SA/LW registry, is requesting the capability close outstanding shipments by entering a Document Nbr.   This is required as there are many intransit shipments that are not being auto-closed.</p> <p><strong>Recommended</strong> <br /> The system should allow the user to enter the Document Nbr for the shipment, review the outstanding items (they would all be checked as the default), permitting the user to un-check any item that has not been confirmed as received, then select update with the system closing all items associated with the Document Nbr.  This change would improve the process and reduce the amount of time required to close intransits.</p> <p><strong>Mission Critical</strong> <br /> The current process is very time consuming and takes resources that could be performing other mission duties.</p> <p><strong>Benefits</strong> <br /> This change will reduce the time to manually close an intransit that was not auto-closed.</p> <p><strong>Users</strong> <br /> All users of the SA/LW registry will benefit from this change.</p>
20560Incorporate DLMS 824R Functionality01696EnterpriseLeidosDoneSubmitted: 4/26/2021<p><strong>Description</strong> <br /> DPAS does not provide support for the DLMS 824R (Reject Advice).  The Army is planning to implement DLMS 824R generation/reporting of data errors for TPF transactions (DLMS 527D) that GCSS-Army does not successfully inbound by August 2021.  This SCR is to develop the processes DPAS requires to support the DLMS 824R Transaction Set.</p> <ol> <li>The DLMS 824R supports the of MILSTRAP related DLMS transactions, and  other DLMS supply, contract administration and logistics bills transactions, but does not replace procedures for error identification addressed by the DLMS 140A Small Arms and Light Weapons (SA/LW) Reporting, DLMS 870S Supply Status, or DLMS 842A/R DoD Supply Discrepancy Report Reply. The DLMS 824R is also used by DLA Transaction Services for narrative message type rejects for all DLMS transactions subject to rejection by DAAS narrative messages</li> <li>This transaction set is not used to reject a DLMS transmission due to ASC X12 syntax errors that DAAS reports via email.  The DLMS 824R that will be received will come from the trading partner system from their inability to process the transaction for reasons other than what is currently supported by the DoD Supply Discrepancy Report (SDR) process (DLMS 842). </li> </ol> <p><strong>Recommended</strong></p> <ol> <li>Modify the DLMS inbound process to inbound the DLMS 824R notifying DAAS of the support and desired format that DPAS anticipates accepting the DLMS 824R transaction set (XML).</li> <li>Develop logic to route the Reject Advice to the correct module / recipient (PA, WM, MM, DPAS Admin) using the DLMS Transaction Set and Document Nbr of the transaction set that was rejected, and the reason for the reject. </li> <li>Provide a user view of the rejected transaction to the user (code and text) provided in the DLMS 824R along with pertinent info from the original DLMS transmission, with the capability to mark the transaction as New (Default when a new reject is added), Read (when a user has viewed the transaction), In Process (provide the user with a text field to denote who was assigned to action the reject advice), and Resolved (with a text field for the user to denote action taken) - drops off the view when marked resolved. </li> <li>The dashboard of each module should be updated to include open DLMS rejects.</li> <li>The design for supporting the DLMS 824R Reject Advice transaction set should provide methods for making the DPAS user as well as the receiving system that generated the reject advice ‘whole’.  This may include providing for the modification of the original data that caused transaction to be rejected, and the resubmission of the DLMS transaction, and in other instances it may include providing the capability to reverse/void the original action the user took providing the appropriate DLMS transactions to the receiving system to make them whole. The actual development of the processes required to make both parties whole may not be in scope for the initial fielding of this SCR given the number of transaction sets that can be rejected via the 824R.  When resources are available, the initial implementation of this capability should be to support the DLMS 527D reject notices.</li> </ol> <p><strong>Mission Critical</strong> <br /> Yes. To support DPAS DLMS compliance, DPAS needs to inbound 824Rs</p> <p><strong>Benefits</strong> <br /> Provide DPAS and its customer with visibility and resolution of DLMS data errors.</p> <p><strong>Users</strong> <br /> This change affects customers/users who are generating DLMS transactions as part of the  business processes.</p> <p> </p> <p><strong>Completed - Release 2021.3 - 10 September 2021</strong></p>
20559DPAS Real Property upload tool01695EnterpriseUSMC: MCCSNewSubmitted: 4/22/2021<p><strong>Description</strong> <br /> USMC MCCS has a need to systematically update their Real Property that is being managed with DPAS with critical information that is maintained and is available from the USMC real property system.  The data that MCCS requires is not available from the RPIM / DAIS data that DPAS currently imports, or is only updated once a year which does not meet the MCCS requirement in managing its real property facilities / projects.</p> <p><strong>Recommended</strong> <br /> DPAS will develop a real-time import process that provides the capability to upload real property data that will be validated, then applied to existing real property records.</p> <p><strong>Mission Critical</strong> <br /> Yes, without this information DPAS does not fully support USMC MCCS's business needs. It has been endorsed by the DPAS PM as part of supporting USMC NAF.</p> <p><strong>Benefits</strong> <br /> Provides additional information for the customer's real property records and improves the accuracy of those records</p> <p><strong>Users</strong> <br /> Yes, all USMC Real Property users.  It should also be usable by Defense Agencies that utilize USMC facilities that are managing their portion of the Real Property using DPAS.</p>
20558DPAS GEX Data Feed01694EnterpriseUSSOCOMNewSubmitted: 20 April 21<p><strong>Description</strong> <br /> Request to establish a Naval Special Warfare (NSW) interface to transfer NSW DPAS data from DPAS POR to NSW Data Environment via established GEX channel. Currently receiving DPAS SOLMS data, but need to refine data requirements to NSW scope.</p> <p><strong>Recommended</strong> <br /> Mirror SOLMS interface within scope of NSW data requirements. Replace SOLMS data file with NSW interface data file for relay via established GEX channel. Supporting documents can be sent via encrypted email or SAFE file transfer; please provide email address for receipt and ticket number to reference. To include: data requirements (xlsx), GEX interface agreement (pdf), SOLMS interface WPHRI09 - Asset Data Visibility Feed (pdf), and NSW Data Environment (NDE) ATO.</p> <p><strong>Mission Critical</strong> <br /> Mission critical. NSW Data Environment (NDE) is a consolidated data engineering solution, pioneered and directed by Naval Special Warfare Command, that manages the integration, storage, and distribution of authoritative data from disparate data sources in order to model and analyze data efficiently and effectively. The NSW Operational Data Store (ODS) and the NSW Enterprise Data Warehouse (EDW) are components of the NDE. The NDE data as a service (DaaS) provides mission essential data to a wide variety of approved NSW and US Special Operations Command (USSOCOM) enterprise business systems, analytics tools, business and artificial intelligence, machine learning algorithms and statistical models, robotic process automation, resource management suites, software applications, data lakes, and data marts within the “hub and spoke” model of the Special Operations Forces Data Environment (SDE). The solution supports Special Operations Forces critical ability to develop enhanced situational understanding, fully inform options for decision makers, and wield influence when and where necessary.</p> <p><strong>Benefits</strong> <br /> ISO CNO FRAGO to implement digital competitive advantage to improve accuracy and accountability for DPAS. The solution supports Special Operations Forces critical ability to develop enhanced situational understanding, fully inform options for decision makers, and wield influence when and where necessary.</p> <p><strong>Users</strong> <br /> All. Allows for visual reporting at all levels.</p>
20557Conversion spreadsheet load by users for Multiple AUIC/UIC01693EnterpriseAF: SPT EQUIPNewSubmitted: 20 April 21<p><strong>Description</strong> <br /> Currently if any mass updates or uploads need to be processed, users are required to submit to DPAS via conversion spreadsheet. Then the user needs to wait for the Leidos team has run the file through validation, send the errors for correction and then resubmitted and finally uploaded. </p> <p><strong>Recommended</strong> <br /> Provide a capability for users to be able to upload conversion spreadsheets for validation and upload.</p> <p><strong>Mission Critical</strong> </p> <p><strong>Benefits</strong> <br /> Reduces workload for DPAS contract support and time that users waits until file is finally uploaded.</p> <p><strong>Users</strong> <br /> ALL</p>
20556UIC applied priority table01692FSMAF: SPT EQUIPNewSubmitted: 20 April 21<p><strong>Description</strong> <br /> FSM Auth On/Hand report does not break down which authorization id is short or excess. The current report gives a role up for the total allowable quantity and the FReq OReq OAuth for that specific Auth-id.</p> <p><strong>Recommended</strong> <br /> Create a reference table that identifies where the on-hand balance should be applied as the UIC prioritization table outlines</p> <p><strong>Mission Critical</strong> </p> <p><strong>Benefits</strong> </p> <p><strong>Users</strong> </p>
20555DRRS report file01691EnterpriseAF: SPT EQUIPNewSubmitted: 20 April 21<p><strong>Description</strong> <br /> The Air Force needs a file to report the unit readiness status to DRRS based on the data in PA and FSM.</p> <p><strong>Recommended:</strong><br /> Push report  that combines on-had and authorization quantities to DRRS or have it available to pull. Specific data fields are required on the report</p> <p><strong>Mission Critical</strong> <br /> Services are mandated to report DRRS readiness capabilities IAW CJCSI 3401.02B</p> <p><strong>Benefits</strong> <br /> Improves accuracy and accountability for DRRS readiness reporting</p> <p><strong>Users</strong> <br /> Yes</p>
20554Supervisory Master Data manager role01690EnterpriseAF: SPT EQUIPNewSubmitted: 20 April 21<p><strong>Description</strong> <br /> Anyone with access to the Master Data tab can load or change the Organizational Data Elements for a UIC such as the FAD. IAW CJCSI 4110.01E 'Service Chiefs are required to implement policies, conduct administrative audits and inspections to eliminate and prevent abuse, misinterpretation and misapplication of UMMIPS.</p> <p><strong>Recommended</strong> <br /> Create a profile as a Supervisory Master Data Manager. This role would be the only profile that can make FAD updates or create a FAD 1 UIC.</p> <p><strong>Mission Critical</strong> <br /> IAW CJCSI 4110.01E the Service Chiefs are required to develop and implement policies on the use of and oversight of all FAD codes assigned to units.</p> <p><strong>Benefits</strong> <br /> Improves accountability</p> <p><strong>Users</strong></p>
20553Registry Recon Status in PA01689EnterpriseAF: SPT EQUIPNewSubmitted: 20 April 21<div><strong>Description</strong> <br />AF/A4LR requires an Agency level, MAJCOM and AUIC level report in Property Accountability that provides the reconciliation status of SA/LW reported in the Registry.<br /><br /></div> <div><strong>Recommended</strong> <br />Create a similar report as the one in the Registry or push the report from the Registry to PA on the dashboard. Or identify the status on the property record. Allowing users to create an ad-hoc report with a filter option on the main Asset Inquiry page. <br /><br /></div> <div><strong>Mission Critical</strong> <br />The equipment managers in the AF deem it as mission critical, as they need this information to sufficiently manage SA/LW on equipment accounts. <br /><br /></div> <div><strong>Benefits</strong> <br />Improves accountability.<br /><br /></div> <div><strong>Users</strong> <br />All users</div>
20552FAD Validation ILS-S Interface01688EnterpriseAF: SPT EQUIPNewSubmitted: 20 April 21<p><strong>Description</strong> <br /> The Master Data Manager profile allows users with access to manually load, update and delete a AUIC/UIC</p> <p><strong>Recommended</strong> <br /> Recommend an interface to the Integrated Logistics System-Supply (ILS-S) UIC/FAD table to automate the FAD application to the UIC in the Master Data file.</p> <p><strong>Mission Critical</strong> <br /> The equipment managers in the AF deem it as mission critical, as a units FAD code helps the order of importance a unit has as it pertains to procurements and future acquisitions. </p> <p><strong>Benefits</strong> <br /> Improves accountability, accuracy and oversight.</p> <p><strong>Users</strong> <br /> All users</p>
20551Receive/Accept Multiple Items01687EnterpriseAF: VSCOSNewSubmitted: 20 April 2021<p><strong>Description</strong> <br /> The Due-In/Receive/Accept process is very time consuming because all items must individually process.  Additionally, all AF Vehicle Management activities order most parts for specific vehicles and current process does not allow the user to mark items against an Asset ID.</p> <p><strong>Recommended</strong> <br /> Recommend adding the option to create Due-Ins and Receive/Accept multiple items in a single transaction under a single Document Number.  Additionally, request adding a "Mark For" field to the receiving process allowing the user to select available assets (vehicles) from the linked Maintenance Activity.  Vehicle selection needs to reflect on the Open Actions dashboard and transfer to all inventory listings. Lastly, request adding Priority Codes to prioritize different vehicle statuses.</p> <p><strong>Mission Critical</strong> <br /> The Air Force vehicle community mandates per Air Force Instruction 24-302, Vehicle Management Chapter 5, all vehicle management activities must track and verify status of parts for all Non-Mission Capable vehicles.  The recommendation of grouping items and displaying Asset ID's will streamline requirement.</p> <p><strong>Benefits</strong> <br /> Grouping items and processing in a single transaction will accelerate practices and streamline tracking procedures.  Additionally, the "Mark For" and Priority Labels facilitates mandated reconciliation practices.</p> <p><strong>Users</strong> <br /> This change will improve part processing operations for all 8,000 Air Force Vehicle Management community warehouse users.</p>
20550Substitute Stock Number01686EnterpriseAF: VSCOSNewSubmitted: 20 April 2021<p><strong>Description</strong> <br /> The Substitute Stock Number feature does not work across all the functions of the Warehouse module.</p> <ol> <li>Maintenance Issue requests for obsolete items requires cancellation and resubmission.</li> <li>Cannot replace SKO Components with compatible items and changing the SKO catalog affects all other kits sharing same configuration.</li> </ol> <p><strong>Recommended</strong> <br /> The Substitute Stock Number function allows the user to issue compatible Stock Numbers during the Maintenance Issue process and replace compatible components within a SKO kit through the Inventory Update process.</p> <p><strong>Mission Critical</strong> <br /> The Air Force vehicle community mandates Materiel Control personnel, Warehouse users, via Air Force Instruction 24-302, Vehicle Management to properly charge vehicle parts against vehicle Work Orders.  Additionally, instruction mandates properly inventorying and managing tool kits.</p> <p><strong>Benefits</strong> <br /> Improves data accuracy and tool/part accountability while streamlining procedures.</p> <p><strong>Users</strong> <br /> This change will streamline Maintenance Issue and SKO management procedures for all Air Force vehicle management Warehouse users</p>
20549Return Items from M&U to WH01685EnterpriseAF: VSCOSNewSubmitted: 20 April 2021<p><strong>Description</strong> <br /> The Maintenance Issue process does not allow returning parts to the Warehouse after issuing to a Maintenance Activity.  Prevents wrong parts issued to Maintenance and Utilization being returned to the Warehouse inventory location or back to the vendor.</p> <p><strong>Recommended</strong> <br /> Create the option to return issued items back to the Warehouse module.  Returned items need to create an open action for Warehouse users to assign an inventory location or send back to the vendor.</p> <p><strong>Mission Critical</strong> <br /> The Air Force vehicle community mandates Materiel Control personnel, Warehouse users via Air Force Instruction 24-302, Vehicle Management to properly charge (issue) parts and materiel within the Fleet Management Information System (i.e., DPAS).</p> <p><strong>Benefits</strong> <br /> Solution will increase accuracy of inventory items and enable proper accountability of sustainment funds.</p> <p><strong>Users</strong> <br /> This change will improve part management for all Air Force vehicle management users performing Maintenance Issues between Warehouse and Maintenance and Utilization modules.</p>
20548Maint Issue Deferred Location ID01684EnterpriseAF: VSCOSNewSubmitted: 20 April 2021<p><strong>Description</strong> <br /> The Maintenance and Utilization Asset Deferred Parts Inquiry or the Warehouse Maintenance Issue Deferred Inquiry displays a location field making reconciliation process difficult and requires the use of multiple inquiries.</p> <p><strong>Recommended</strong> <br /> Recommend adding a location field to the Warehouse Maintenance Issue Deferred Inquiry and the Maintenance and Utilization Asset Deferred Parts Inquiry to aid inventory validation process.</p> <p><strong>Mission Critical</strong> <br /> The Air Force vehicle management community mandates per Air Force Instruction 24-302, Vehicle Management for Materiel Control personnel to manage, monitor, and reconcile deferred maintenance work orders.</p> <p><strong>Benefits</strong> <br /> Implementing solution will save time and improve the accuracy of periodic deferred maintenance reconciliations.</p> <p><strong>Users</strong> <br /> This improvement would affect all Air Force vehicle management users utilizing the Maintenance Issue process to defer parts between the Warehouse and Maintenance and Utilization modules.</p>
20547Add delete capability to Due before under the inspection tab01683WarehouseAF: AFERMSNewSubmitted: 14 Apr 21<p><strong>Description</strong> <br /> Currently unable to simply click an X to delete the date in the due before block of the search criteria. You have to highlight and click delete</p> <p><strong>Recommended</strong> <br /> Add the X delete button in the Due Before block to save highlighting and clicking delete or backspacing the date out.</p> <p><strong>Mission Critical</strong> <br /> important</p> <p><strong>Benefits</strong> <br /> Saves clicks and back spacing</p> <p><strong>Users</strong> <br /> all AFERMS</p>
20546Regional Customer Assistant Role Real Time Reports01682WarehouseUSMCDoneSubmitted: April 8, 2021<p><strong>Description</strong> <br /> The customer regional assistant role (DPAS 9150) does not have access to the “Inv OH/Issued” Real time reports. See attached screenshots of the real time reports screen for each role. We are being forced to give our data analyst who don’t transact transactional access to view these reports. <br /> We are requesting that this role be updated to include these two real time reports. Please let Rick McMillan or myself know if there are questions.</p> <p><strong>Recommended</strong> <br /> Update the Regional Customer Assistant role to include the "Inv Oh/Issued" Real Time Reports.</p> <p><strong>Mission Critical</strong> <br /> We are being forced to give our data analyst who don’t transact transactional access to view these reports.</p> <p><strong>Benefits</strong> <br /> Auditing purpose.</p> <p><strong>Users</strong></p> <p><strong>Completed -- Release 2021.2 - 28 May 2021</strong></p>
20545Printing Capability01681WarehouseUSMC: CSPNewSubmitted: 6 Apr 2021<p><strong>Description</strong> <br /> Currently only in the warehouse transfer process can you print an 1348 or an 1149.  All other shipping processes it's either an 1348 or 1149 there is no option for both.</p> <p><strong>Recommended</strong> <br /> Recommend the following requirements.<br />All shipping processes Material Release Orders or Warehouse Issues have the capability to print out both a 1348 or an 1149.</p> <p><strong>Mission Critical</strong> <br /> Yes, having this functionality will help with the shipping process instead of warehouses being required to manually create 1348's or 1149's.</p> <p><strong>Benefits</strong> <br /> Having this functionality will help speed up the shipping process for the CSP.</p> <p><strong>Users</strong> <br /> Yes All.</p>
20544DLA Reports01680WarehouseDLANewSubmitted: 04/06/2021<p><b>Description</b> <br /> Request three additional reports be created for the DLA Distribution Warehouse level. See attachment. This will involve a few new data elements.</p> <p><b>Recommended</b> <br /> Update DPAS logic and create DLA Inventory by location, DLA receipt, and DLA Issue reports</p> <p><b>Mission Critical</b> <br /> Yes, to enable the current DLA Distribution standard logic</p> <p><b>Benefits</b> <br /> To ensure standardization for the DLA and VA storage and distribution agreement</p> <p><b>Users</b> <br /> Yes, for DLA Distribution</p>
20543Add UIT Designator01679EnterpriseLeidosNewSubmitted: 4/6/2021<p><strong>Description</strong> <br /> The DLMS committee approved a new UIT Program Designator to provide for Services to manage items serially when they have a requirement to do so. <br /> Per ASC 1317 - This change establishes a new Unique Item Tracking (UIT) Program/ Designator Code AAK – Other Serially Managed Items. This UIT program will be used to account for Service-owned, serially managed items, to include capital equipment, where existing UIT Programs do not apply.</p> <p><strong>Recommended</strong> <br /> Add new value to the DPAS.CAT.UIT_DESIGNATOR_LKP <br /> AAK – Other Serially Managed Items.</p> <p><strong>Mission Critical</strong> <br /> Yes.  Approved DoD Change</p> <p><strong>Benefits</strong> <br /> Provides for services to serially managed items they have a need to manage serially.</p> <p><strong>Users</strong> <br /> This change is applicable to all DPAS customers.</p>
20542Inventory Over Under Site change report01678WarehouseAF: AFERMSNewSubmitted: 5 Apr 21<p><strong>Description</strong> <br /> The Inventory Over Under report currently creates a different Excel sheet for each Warehouse when ran by tier level Site or above.   For data analysis, we need all the data in a single sheet for all warehouses while still retaining the ability to separate the data by warehouse when needed.</p> <p><strong>Recommended</strong> <br /> Give the option to output the data in a combined spreadsheet without the Warehouses in different Excel sheets. </p> <p><strong>Mission Critical</strong> <br /> critical. otherwise personnel will have to pull multiple reports for warehouses at same location to submit for competing funding</p> <p><strong>Benefits</strong> <br /> reduced errors and manpower savings.</p> <p><strong>Users</strong> <br /> all AFERMS</p>
20541Add Inspection Type Column01677WarehouseAF: AFERMSNewSubmitted: 23 Mar 2021<p><strong>Description</strong> <br /> Currently unable to determine which type of inspection is due under inspection. Material Mgmt, Inspections tab</p> <p><strong>Recommended</strong> <br /> Under the Search criteria add</p> <p><strong>Mission Critical</strong> <br /> important</p> <p><strong>Benefits</strong> <br /> Ability to schedule more than one different class when they have a different start time. </p> <p><strong>Users</strong> <br /> all AFERMS</p>
20540Upload KSD's01676WarehouseUSMC: CSPNewSubmitted: 19 March 2021<p><strong>Description</strong> <br /> Currently in DPAS-WM there is not one central location were Key Supporting Documents (KSD's) can be uploaded.  This would facilitate audit and/or research if a central location was provided for all KSDs. </p> <p><strong>Recommended</strong> <br /> Recommend to have the ability to upload all Key Supporting Documents (KSD's) in the Inquiries>Document area. </p> <p><strong>Mission Critical</strong> <br /> Yes, Installations and Logistics HQMC is developing an order stating all Key supporting Documents need to be uploaded into the APSR.</p> <p><strong>Benefits</strong> <br /> Having this type of functionality or ability will reduce times and improve accountability when searching for multiple Key Supporting Documents.  It will also help during an Audit when you have all Key Supporting Documents in one Area.</p> <p><strong>Users</strong> <br /> All IIF & UIF</p>
20539Add Attachment to Member Profile01675WarehouseAF: AFERMSNewSubmitted: 16 Mar 2021<p><strong>Description</strong> <br /> Member Profile needs the ability to attach information. For example, members have to have an authorization letter signed by the flight doctor to fly with NVD. We would be able to attach this letter to the profile and when the member changes units, his authorization letter would already be in his records.</p> <p><strong>Recommended</strong> <br /> use the same concept as we do for inspections or any of the other ways we attach items, put  a check box  so when you check that profile the attachment button pops and you can add attachment.</p> <p><strong>Mission Critical</strong> <br /> important</p> <p><strong>Benefits</strong> <br /> time savings, and tracking made easier</p> <p><strong>Users</strong> <br /> all AFERMS</p>
20538Add Different Appointment Times01674WarehouseAF: AFERMSNewSubmitted: 16 Mar 2021<p><strong>Description</strong> <br /> we are not able to set appointment time because appointment intervals are mandatory.</p> <p><strong>Recommended</strong> <br /> provide ability to have set appointment times versus appointment intervals</p> <p><strong>Mission Critical</strong> <br /> important</p> <p><strong>Benefits</strong> <br /> Ability to schedule more than one different class when they have a different start time. </p> <p><strong>Users</strong> <br /> all AFERMS</p>
20537Check Box for Admin01673WarehouseAF: AFERMSNewSubmitted: 16 Mar 2021<p><strong>Description</strong> <br /> Size category generates a walk in even if you are doing an admin only.</p> <p><strong>Recommended</strong> <br /> add check box or drop down for admin only when scheduling is in use.</p> <p><strong>Mission Critical</strong> <br /> important</p> <p><strong>Benefits</strong> <br /> Ability to schedule more than one different class when they have a different start time. </p> <p><strong>Users</strong> <br /> all AFERMS</p>
20536End Of Active Service Outstanding Items Inquiry01672WarehouseUSMC: CSPNewSubmitted: 3/11/2021<p><strong>Description</strong> <br /> Currently, the Consolidated Storage Program (CSP) has a problem with Marines leaving active duty service with gear on their account. The CSP has been writing this gear off during the their annual audits, but there is a desire to create an End of Active Service (EAS) inquiry that will show all the returnable assets on a Marines account when they hit a predetermined amount of service time left.</p> <p><strong>Recommended</strong> <br /> Create an EAS Inquiry that will populate all the items left on a Marines account when they are 180 days away from their EAS date. Having a six month time frame will ensure that the Marines are notified well in advance of their exit date. </p> <p><strong>Mission Critical</strong> <br /> Yes, this inquiry will allow the CSP to notify the Marines of outstanding issues, which in turn will hold the Marines accountable to turn it in before leaving the service. This will also allow the CSP to conduct analysis on the each warehouse and the amount of outstanding gear not turned in.</p> <p><strong>Benefits</strong> <br /> Implementing this inquiry will help reduce the amount of gear that is lost due to Marines who leave the service with outstanding turn ins. That directly affects financial cost due to having to replace lost/missing gear.  </p> <p><strong>Users</strong> <br /> This will effect all CSP Users and the customers we issue gear to.</p>
20535Manufacturer Lot and Contract Numbers on Pick Ticket01671WarehouseUSMC: CSPNewSubmitted: 3/10/2021<p><strong>Description</strong> <br /> Currently, when the Consolidated Storage Program (CSP) moves items that have a manufacturer lot and contract number they have to write those attributes on the pick ticket. Would recommend these fields be included on the pick sheet so they will no longer have to manually write it.</p> <p><strong>Recommended</strong> <br /> Include the manufacturer lot and contract numbers on the pick ticket that is generated. If the asset is not lot or contract managed then the fields can be blank.</p> <p><strong>Mission Critical</strong> <br /> Yes, including these attributes will save CSP users time when moving assets within the warehouse.</p> <p><strong>Benefits </strong> <br /> Including these attributes will save CSP users time when moving assets within the warehouse.</p> <p><strong>Users</strong> <br /> This will effect all CSP Warehouses.</p>
20534FSM LIN/TAMCN / Stock Number01670FSMLeidosNewSubmitted: 3/8/2021<p><b>Description</b> <br /> Authorizations are redundant and problematic in PA for centrally managing authorization quantities and overall force management. </p> <p><b>Recommended</b> <br /> Move all PA authorizations to FSM.  Stock Number Authorizations and LIN/TAMCN Authorization for more cohesive management.  </p> <p><b>Mission Critical</b> <br /> Yes for tech refresh.  </p> <p><b>Benefits</b> <br /> Mass update capabilities, unit deployments, Theater Force Management.  </p> <p><b>Users</b> <br /> No</p>
20533Implement ADC 1379 changes in Materiel Mgmt and Warehouse to support a Warehouse Project Code01669EnterpriseLeidosNewSubmitted: 03/03/2021<p><strong>Description</strong> <br /> This SCR implements the Project Code change identified within ADC 1379.  For the Cost Center change identified within ADC 1379, reference ASA(ALT)'s DPAS SCR 01562.  Project Code requirement - USSOCOM purchases service funded inventory.  Once it arrives and is placed in stock, each service's inventory is given a different project code to identify the qty that each service has purchased and will be subsequently issued. Today, there is no capability to pass a requisition Project Code (why the customer is ordering the item) and the Project Code that is assigned to the inventory (what stock needs to be selected to fill the order).  Today to support sending the warehouse project code, the customer cannot cite a project code in the order.  To support USSOCOM's requirement of segregating the inventory, there was a need for the second Project Code to be included in the messaging between the Materiel Mgmt and Warehouse Mgmt modules.</p> <p><strong>Recommended</strong> <br /> Warehouse Project Code - Within Materiel Mgmt., include the warehouse and requisition project codes in the DLMS 940R transaction that is sent to the warehouse for fulfillment.   For the Warehouse, process the inbound 940R adding the warehouse project code to the MRO.  Then use the warehouse project code to determine stock availability and to feed to Materiel Selector and in the creation of the Pick row that is subsequently created.  On the outbound DLMS 945A distinguish include the requisition's project code and the warehouse project code. Use the warehouse project code to decrement stock in Materiel Mgmt. upon receipt of the DLMS 945A confirming the shipment of the stock. The DLMS 856S shipment status will contain the requisition project code.   When the order fulfillment is to occur with inventory consisting of multiple warehouse project codes, permit the suffixing of the Document Nbr to enable multiple MROs to be generated to the same RSA, each with a different warehouse project code. This change may require a change to the Picking process.</p> <p><strong>Mission Critical</strong> <br /> Yes.  USSOCOM requires a method to mange their inventory by the organization that purchased it.</p> <p><strong>Benefits</strong> <br /> ADC 1379 eliminates the confusion between the requisition project Code (why the organization is ordering the item) and how the warehouse is storing the item.  The Materiel Manager / Warehouse operations will now be able to segregate the materiel without having to email/notify the warehouse which stock to select to fill an order.</p> <p><strong>Users</strong> <br /> Most warehouse operations will benefit by this change.</p>
20532Reason Code MILSTRIP Code Change01668WarehouseUSMC: CSPNewSubmitted: 2/26/2021<p><strong>Description</strong> <br /> Currently, during the individual return process all MILSTRIP transactions created for lost gear is a D7A. This MILSTRIP Transaction does not meet Marine Corps Standards for audit. The concern is that a D7A is an issue transaction instead of a loss transaction, which is what the Marine Corps needs to see during audit inspections. The attached spreadsheet is the preferred MILSTRIP transactions the Marine Corps would prefer to see be created when an individual doesn't return gear. This would make the non-returned items audit compliant.</p> <p><strong>Recommended</strong> <br /> Change the non-returned items reason codes MILSTRIP transactions to match the values in the attached spreadsheet. </p> <p><strong>Mission Critical</strong> <br /> Yes, this would ensure that a MVGL would be generated for the correct non returned reason codes when that SCR is put into production.  These transactions on the MVGL would ensure the commander would correctly identify losses when vouchering the MVGL.  This would make them more accurate and meet audit standards.</p> <p><strong>Benefits</strong> <br /> This SCR improves accuracy, accountability and audit readiness/financial reporting.   USMC audit keys in on correctly identifying losses, and the causes of those losses.   Being able to quickly identify losses due to non-return of previously issued assets, would be a significant improvement to the audit process. </p> <p><strong>Users</strong> <br /> This will affect all users in CSP and should be a net benefit to other services and organizations that issue equipment as well. </p>
20531USMC DAI Interface01667WarehouseUSMC: CSPNewSubmitted: 2/26/2021<p><strong>Description</strong> <br /> Currently, the Consolidated Storage Program (CSP) doesn't have an interface for financial transactions. In October 2021 the Marine Corps will move from the Standard Accounting, Budgeting, and Reporting System (SABRS) accounting system to Defense Agencies Initiative (DAI) Enterprise Resource Planning (ERP) system.  We would like to interface the new Marine Corps accounting system (DAI) with DPAS. This will allow for transactions to flow seamlessly between systems, unlike the current process that demands ordering through DPAS and then "Swivel Chairing" to SABR's to obligate funds.</p> <p><strong>Recommended</strong> <br /> Create an interface between DPAS and DAI. Currently GCSSMC is looking at creating a outbound XML file using the "piping" delimiter as field separator. DPAS should be able to follow a similar business process. </p> <p><strong>Mission Critical</strong> <br /> Yes, interface would help ensure accuracy for obligating funds and save personnel work hours.</p> <p><strong>Benefits</strong> <br /> This interface would help ensure accuracy for obligating funds and save personnel work hours.  This would also be a significant improvement for audit. </p> <p><strong>Users</strong> <br /> This will effect all CSP Warehouses that order assets.  This will likely be a net benefit to other services and organizations as DIA is not USMC specific. </p>
20530Add Location and Container to the Repair Part Consumption Report01666WarehouseAF: AFERMSDoneSubmitted: 25 Feb 2021<p><strong>Description</strong> <br /> Need to add location and container to the Repair Part Consumption Report.</p> <p><strong>Recommended</strong> <br /> Under Repair Part Consumption Report, we need to add two columns, one for Location the repair part was pulled and the same for the Container the repair part was pulled.</p> <p><strong>Mission Critical</strong> <br /> YES! Warehouse technicians have no idea where the part was pulled from to receive it back to once the part is placed in due out status. Also if a container is deployed and it returns, you understand on what is needed to refill the deployed container.</p> <p><strong>Benefits</strong> <br /> data accuracy.</p> <p><strong>Users</strong> <br /> All</p> <p><strong>Completed -- Release 2021.2 - 28 May 2021</strong></p>
20529DPAS to EBiz Interface Codes01665PADFASNewSubmitted: 2/22/2021<p><strong>Description</strong> <br /> Due to an audit finding we have an issue where the document number and obligating document number in DPAS only transfers to eBiz with the x819 transactions.<br /> The document number and obligating document number for x815 and x817 transactions do not appear on the interface file as these fields are currently optional.</p> <p><strong>Recommended</strong> <br /> The document number and obligation document number for x815 and x817 transactions should be mandatory and pulled in on the interface file to e-Biz to populate the Register Document Number in e-Biz.</p> <p><strong>Mission Critical</strong> <br /> This is a mission critical function as it is causing an audit finding.</p> <p><strong>Benefits</strong> <br /> The benefit of implementing this change will reduce process time for accounting technicians to manually input the document number for capital transactions.  Additionally, it will improve the accuracy of the financial statements because eBiz will receive the data from DPAS and reduce the risk of input errors.</p> <p><strong>Users</strong> <br /> Will affect all users within DFAS.</p>
20528Event Manager01664WarehouseLeidosNewSubmitted: Feb 18 2021<p><strong>Description</strong> <br /> Create a admin page that will allow Leidos personnel to monitor failed events, review the failed event details, and re-queue the failed events from the GUI. Currently this involves database queries to determine a failed event and then a script from each team to re-queue the events.</p> <p><strong>Recommended</strong> <br /> Add a screen to the admin module to allow Leidos personnel to monitor and re-queue failed events.</p> <p><strong>Mission Critical</strong> <br /> Yes. Will help to quickly turn around failed events.</p> <p><strong>Benefits</strong> <br /> Reduces time on writing scripts for failed events.</p> <p><strong>Users</strong> <br /> Yes.</p>
20527Account Transfers01663PADISANewSubmitted: 17 Feb 2021<p><strong>Description</strong> <br /> Organizations within DISA are re-organizing and assets are required to be transferred to the appropriate UIC/Custodian Account using Asset Management transfer. We would like the option to transfer sub-custodian user hand-receipts along with sub-accounts. Parent child relationship.</p> <p><strong>Recommended</strong> <br /> Request Property Custodian (PC) the capabilities to transfer all sub custodian number hand receipts when these assets are transferred to newly created hand receipt. This will eliminate the requirement for the PC to re-create new sub custodian hand receipts if remain the same.</p> <p><strong>Mission Critical</strong> <br /> Adding this option is not mission critical or mandated, just makes it more efficient.</p> <p><strong>Benefits</strong> <br /> This will reduce man-hours and cost due to rekeying information. The Property Custodian (PC) will be given the option to maintain same user hand receipt without re-creating new sub custodian hand receipts due to re-organization of directorate assets.</p> <p><strong>Users</strong> <br /> Yes, this action affects all users within the Agency.</p>
20526DISA COAMS Location Interfacing01662EnterpriseDISANewSubmitted: 16 Feb 2021<p><strong>Description</strong> <br /> DISA is requesting the Defense Property Accountability System (DPAS) Program Management Office (PMO) to modify the DPAS application to interoperate with other DISA and DOD systems that use location and other enumerations from the Cyber Operational Attribute Management System (COAMS).  Once modifications are made, DISA will be able to use data from DPAS to update other systems, and data from other systems to update DPAS eliminating both duplication of effort and inconsistent data between systems.</p> <p><strong>Recommended</strong> <br /> Integrate DPAS with COAMS so that users can create new sub-organizations and sub-locations in COAMS via DPAS by using a DPAS-COAMS interface. Similar to the Real Property Identification interfacing located under the Master data/location. See attach COAMs Integration Levels.</p> <p><strong>Mission Critical</strong> <br /> This action is critical to enhance DISAs asset location in support of audit.</p> <p><strong>Benefits</strong> <br /> Enable external systems to query DPAS using a web service to recover owning organization and locations for IT Assets using the affected Fully Qualified Domain Name (FQDN) or Serial Number (SN).  It centralizes data and improves accuracy of asset location to minimize rekeying errors.</p> <p><strong>Users</strong> </p>
20525USMC Asset Data Feed01661EnterpriseUSMCDoneSubmitted: 2/10/2021<p><strong>Description</strong> <br /> USMC is modernizing their Master Data Repository (MDR). They have a requirement for additional asset / history information from DPAS. Given that DPAS has commenced several initiatives relating to how assets will be managed, DPAS is not able to provide a "To Be" at this time.  For starters, USMC has agreed to accept the 5 Asset Extracts that DPAS currently has with a re look of what can be provided in the future should there be an additional requirement. </p> <p><strong>Recommended</strong> <br /> DPAS provide the 5 Asset Extract feeds for PA and Warehouse (exclude Real Property extracts as they will not contain any data) to USMC.  The files will be made available through DAAS GEX.  It is requested the file be created daily.</p> <p><strong>Mission Critical</strong> <br /> This is mission critical as per guidance for USMC LDS program.</p> <p><strong>Benefits</strong> <br /> Improves USMC asset visibility to accomplish the USMC mission.  Is a Std DPAS extract that is available that have access to DAAS GEX.</p> <p><strong>Users</strong> <br /> This SCR will support the USMC.</p> <p> </p> <p> </p> <p> </p> <p><strong>Completed -- Release 2021.2 - 28 May 2021</strong></p>
20524Add Cu Ft attribute to Stock Nbr Inquiry / Create a Real-Time report01660WarehouseDLANewSubmitted: 2/9/2021<p><strong>Description</strong> <br /> DLA is implementing DPAS for supplies that are managed by COCOs.  The COCOs could have materiel that is warehoused with more than 1 owner.  DLA needs a way to determine warehouse utilization by owner.  To be effective, customer must be diligent in accurately reporting the Unit Cube(ft) of the Unit Of Issue Qty.</p> <p><strong>Recommended</strong> <br /> Add Cu Ft to the Stock Nbr inquiry, and/or develop a real-time report that depicts the following attributes:</p> <ul> <li>warehouse name,</li> <li>stock nbr,</li> <li>item desc,</li> <li>owning dodaac,</li> <li>total on hand qty for Stock Nbr/Owning DoDAAC,</li> <li>unit cube,</li> <li>sum(qty) x unit cube.</li> </ul> <p><strong>Mission Critical</strong> <br /> This is considered essential for managing warehouse utilization.  While nothing is perfect due to how materiel must be stored in the warehouse efficiently and effectively, it does provide a measure of utilization within a warehouse.</p> <p><strong>Benefits</strong> <br /> It provides the customer with a way of looking at Warehouse Utilization / Space Utilization and in determining a cost allocation of the warehouse operations for COCO operations.</p> <p><strong>Users</strong> <br /> This change is considered beneficial for all customers / users of the Warehouse module.</p>
20523FLIS/FEDLOG Update01659EnterpriseLeidosIn ProgressSubmitted: 2/2/2021<p><strong>Description</strong> <br /> Currently when a user adds a new NSN record either by Catalog A/U/D or insert from conversion that does not exist on the DPAS Fedlog tables there is no current process to go to FLIS / FEDLOG to update the record with proper FLIS values or verify if indeed the stock number added is an NSN. I&S and other data may remain incomplete or wrong if user entered incorrectly.</p> <p><strong>Recommended</strong> <br /> Create DPAS to webflis file feed that allows to request records from FLIS to be updated or inserted to DPAS Fedlog tables.  All 13 digit numbers catalog as B should be sent.  If FLIS finds a match and responds with data, data should be inserted to Fedlog tables.  Background process should then update Stock Number types of B to A then update to fedlog values including I&S data.  All 13 digit Stock Number types of A that do not have Fedlog records should be updated in the same fashion.  Additional step in the background process would be to retrieve I&S stock numbers not in DPAS Fedlog tables.  Records that have Parents or children with no Fedlog record should be processes with rules above or set in a holding table to request data from FLIS.  Alternative would be to use FEDLOG disks to do a monthly reconciliation if FLIS interface cannot facilitate requests for data.</p> <p><strong>Mission Critical</strong> <br /> Yes currently many customers have incomplete data as well as records that are indeed NSNs that does not have current Fedlog data or wrong data.</p> <p><strong>Benefits</strong> <br /> Customers have valid data from FLIS/DLA centralized source for NSNs.</p> <p><strong>Users</strong> <br /> Yes all users are affected.  Tech Refresh is dependent to deliver better requisition and reporting capabilities future state.</p> <p><strong>Partially Completed - Release 2021.3 - 10 Sept 2021</strong></p>
20522Alpha Character in the 11th position of Document Number01658EnterpriseDoDEANewSubmitted: 28 Jan 2021<p><strong>Description</strong> <br /> Provide DPAS functionality to allow the system to generate document numbers with an Alpha Character in the 11th position:</p> <ul> <li>DoDM 4160.21-V1, October 2, 2019 provides guidance to agencies to process turn-in documents in the DLA Disposition Services web-based Electronic Turn-in Document (ETID) System.  The ETID system generates the document number with alpha character “T” in the 11th position of the document number.</li> <li>DoDEA is required to use this system, to process 1348-1A in order for the DLA Disposition Services (DLA DS) contracted transportation to pick up turn-in property; per the guidance there is no way for DLA DS or DoDEA to track the property if the 1348-1A isn’t generated in their system.</li> <li>The DPAS system does not support document numbers with an Alpha Character in the 11th position.  This has become issue with DoDEA, turn-in documents due to inability to generate identical turn-in document numbers sequence in order to match the document numbers for transaction recondition for audit review/readiness, and the tracking of turn-in documents. DoDEA requires DPAS system to support incorporating the Alpha Character in the 11th position of the document number.</li> </ul> <p><strong>Recommended</strong> <br /> Provide system functionality to auto generate or manually process document numbers with the ability to populate the 11th position with Alpha character. Consider inter-face with DPAS and DLA Disposition Services.</p> <p><strong>Mission Critical</strong> <br /> This request is functionality mission critical for the tracking and reconciliation of turn-in documents number. The DoDM 4160.21-V1 guidance doesn't mandates agencies to use DLA Disposition Services web-based Electronic Turn-in Document (ETID) System to process/generate the 1348-1A document. DoDEA is using the ETID system because when contracted transportation pick up property, there is no way for DLA DS to track the property if is not in their system.</p> <p><strong>Benefits</strong> <br /> The benefit of adding this feature will allow the user to track the transaction with identical data document numbers. It will provide accurate documentation, provide reconciliation/audit trail and allow the user to reduce the amount of time generating additional documents outside of DPAS to explain the circumstance of discrepancy between documents numbers for same transaction.</p> <p><strong>Users</strong> <br /> Yes: This issue affects 100% of all DoDEA's property accountability functional users require to utilize the DLA Disposition Services for the disposal /turn-in process.</p>
20521Modify DLMS 940R Routing01657WarehouseLeidosNewSubmitted: 1-26-2021<p><strong>Description</strong> <br /> The DPAS DLMS Outbound processor checks to see if the DLMS transaction is to be routed internally based upon the RIC or DoDAAC To.  When the RIC or DoDAAC To exists within DPAS, the DLMS transaction is move to the DLMS Inbound folder rather than being placed in the DLMS Outbound folder. With DLA planning to use the DPAS Warehouse module for the management of VA PPE, there is a requirement to feed Transportation Request transactions to VSM which will have the same RIC as the DPAS warehouse (same organization operating VSM and DPAS).</p> <p><strong>Recommended</strong> <br /> Modify the DPAS DLMS Outbound processor to check outbound generated DLMS 940R transactions for a Distribution Code (Industry Code = AK) of '111'.  When true, place transaction in the DLMS Outbound folder for DAAS to pickup.</p> <p><strong>Mission Critical</strong> <br /> Yes.  Without this change, DPAS is unable to route Transportation Request transactions (DLMS 940Rs) to the transportation system when they utilize a RIC that exists within DPAS. This SCR is being submitted in support of the DLA VA PPE project.</p> <p><strong>Benefits</strong> <br /> Enables transaction to be electronically sent to a Transportation Management System.  Without this change, it is not possible when the systems share the same RIC.</p> <p><strong>Users</strong> <br /> This change will only impact customers of the Warehouse module that also operation a separate transportation system that requires the use of the same RIC as the Warehouse. It will have no affect on any other customer.</p>
20520DAI Accounting Interface Report01656EnterpriseMDANewSubmitted: 15 Jan 2021<p><strong>Description</strong> <br /> In order to ensure transactions interface from DPAS to DAI, MDA reconciles reports from both systems.  Currently, DPAS Interface System Initiated report is only available in PDF format and makes it extremely difficult to validate transactions.  The process requires extensive steps in Exporting the PDF to Excel and utilizing formulas to attain necessary information. This is a timely process since Exporting PDF to MS Excel does not convert the same way each time.  Currently, it takes at least 4 man-hours to reconcile transactions between both systems; therefore, currently MDA only reconciles once a month.</p> <p><strong>Recommended</strong> <br /> Converting the report from PDF to Excel will minimize the man-hours required to reconcile the DAI Accounting Interface Report and allow the users to perform the report on a more frequent basis.</p> <p><strong>Mission Critical</strong> <br /> No: This action will allow for a more efficient work flow and minimize the man-hours required to reconcile the report. </p> <p><strong>Benefits</strong> <br /> All agencies that utilize the DPAS and DAI will benefit from the Excel format.  On average it will save at least 3 man-hours each time personnel reconciles reports between DAI and DPAS.   Additionally, reconciliation can be conducted on a more frequent basis (daily or weekly); therefore, any issues between DAI and DPAS will be identified in a timelier basis.</p> <p><strong>Users</strong> <br />This will affect the Accounting/Financial users of DPAS.</p>
20519Administrator Access to DLMS Inquiry01655EnterpriseLeidosNewSubmitted: 01/13/2021<p><strong>Description</strong> <br /> When a production issue occurs with a suspended DLMS transaction, users with the DPAS Admin role are able to see such suspensions but lacks the ability to reprocess one. When conditions are corrected for a previously suspended DLMS transaction to process successfully, it is beneficial for the user with this role to be able to initiate the reprocessing of the transaction. This function is only available to Standard Users at this time, though few understand when and how to use it. In most cases, a DPAS Admin has to contact a user and ask them to go and reprocess a transaction(s) that are suspended. In some cases this has caused issues where the user chooses the wrong transaction to reprocess.</p> <p><strong>Recommended</strong> <br /> Grant access to the DPAS Admin role(s) to enable the reprocessing of DLMS transactions that are suspended within the DLMS Transaction Review page of the ICP module.</p> <p><strong>Mission Critical</strong> <br /> No, as Standard Users are able to perform this function today, the request would not be considered mission critical. This change will enhance Leidos' ability to provide quality support to it's customer base within DPAS.</p> <p><strong>Benefits</strong> <br /> This reduces time for Leidos to resolve Production Issues and improves on the accuracy of those resolutions by removing the "middle man" who could cause further issues.</p> <p><strong>Users</strong> <br /> This should only affect users with a DPAS Admin role within DPAS.</p>
20518Master Data Repository Additions01654WarehouseUSMC: DMCNewSubmitted: 1/4/2021<p><strong>Description</strong> <br /> Requesting that three additional data elements be fed to the Master Data Repository (MDR). <br /> We would like the Catalog Inquiry, the Document Inquiry, and the DLMS Inquiry data be sent to the MDR. Ideally, all available columns from the Inquiry pages would be sent to the MDR.</p> <p><strong>Recommended</strong> <br /> Adding these inquiries to the daily MDR feed.</p> <p><strong>Mission Critical</strong> <br /> Yes, Adding these three inquiries would increase visibility of data to auditors. This would also create a historical archive of our catalogs which would assist in system analysis.</p> <p><strong>Benefits</strong> <br /> Improves data reporting and accountability.</p> <p><strong>Users</strong> <br /> All users in our agency who use the MDR on a daily basis.</p>
20517Duplicate Document Numbers01653WarehouseUSMC: DMCNewSubmitted: 12/16/2020<p><strong>Description</strong> <br /> Secondary Repairable Managers submit documents for repair or return assets to MCLB Albany for adjudication. They also request a replacement asset on the SAME DOCUMENT NUMBER to be returned to them. If the A5 document is worked in DPAS before the assets are picked up in Albany, it causes the receipt document to be PENDING until the A5 documents are shipped.  Once the shipping documents are processed completely, the receipt document can then be processed. <br /> This is causing a backlog of documents to be processed and assets waiting to be adjudicated.</p> <p><strong>Recommended</strong> <br /> Ability for DPAS to have same document for receipt and issue without being associated to each other.  Remove association between A5 and DW for same document number. </p> <p><strong>Mission Critical</strong> <br /> Mission Critical as it is delaying Secondary Repairable Operations. </p> <p><strong>Benefits</strong> <br /> Reduces document back up and assets are able to be stored.</p> <p><strong>Users</strong> <br /> All users.</p>
20516Unit/Individual Reconciliation (Inventory Issued Assets)01652WarehouseSPECWARCOMNewSubmitted: 11 Mar 2017<p><strong>Description</strong> <br /> Unit/Individual Reconciliation (Inventory Issued Assets): Posting the Platoon inventory is ALL or NONE. There should be an option to post a single or multiple serial number(s) and to “not post” any asset that is not accounted for (suspected missing or lost and being searched).</p> <p><strong>Recommended</strong> <br /> Unit/Individual Reconciliation (Inventory Issued Assets): Posting the Platoon inventory is ALL or NONE. There should be an option to post a single or multiple serial number(s) and to “not post” any asset that is not accounted for (suspected missing or lost and being searched).</p> <p><strong>Mission Critical</strong> <br /> Yes. Cannot complete/reconcile Platoon inventory if any item is unaccounted for or in suspected loss/under investigation status.</p> <p><strong>Benefits</strong> <br /> Improves accuracy of issued items.</p> <p><strong>Users</strong> <br />Yes.</p>
20515Daily RIC Master Update Job01651EnterpriseLeidosNewSubmitted: 7 December 2020<p><strong>Description</strong> <br /> DPAS maintains master listings of DoD DoDAACs and RICs within the DPAS FED_LOG database.  DPAS receives a daily DoDDAAC file via DAAS GEX that provides new and updates to existing DoDAACs. DPAS processes the file and updates the DoDAAC Master table. The RIC Master table is not systematically updated.  Today, the DPAS team must take action to update it periodically, thus the RIC Master table is not as current as it could be which can result in processing / validation delays.</p> <p><strong>Recommended</strong> <br /> It has been determined that the RIC data is also included in the daily DODAAC file that is received via DAAS GEX.  RICs are identified within the file as a DODAAC that begin with 'ZZZ'.   For example, a record with a DoDAAC value of 'ZZZA4J' contains the data for RIC 'A4J'.  DPAS needs to develop a process to extract the RIC data from the daily DODDAAC file received via DAAS GEX, and update the RIC Master table.</p> <p><strong>Mission Critical</strong> <br /> Mission Critical, Newly added ICPs are not able to transmit DLMS transactions through DAAS to external trading partners because a it does not pass the RIC validation until DPAS manually updates the RIC Master table with the RIC data.</p> <p><strong>Benefits</strong> <br /> Reduces time and effort/cost  for DPAS (Analyst/DBA analysis) and for the trading Partner (business interruption/analysis).</p> <p><strong>Users</strong> <br /> Newly added ICPs cannot be used until Support updates the RIC Master table with the new RIC(s).  DLMS 527Ds (PMRs/Due In) records are send RIC to RIC.  These transactions require the RIC Master table to be current in order to allow processing to occur.  As more users implement these features, it is imperative that RIC Master table is current.</p>
20514Army Asset Data Feed01650EnterpriseArmyDoneSubmitted: 2020/11/23<p><strong>Description</strong> <br /> Army has a requirement for Asset data for Army owned assets managed using the DoD's  Defense Property Accountability System "DPAS" beyond the data currently provided by the UIT interface.  This data will be used to populate the Army Vantage program to expand Army Vantage's mission set for assets and serials information.</p> <p><strong>Recommended</strong> <br /> DPAS provide the Asset Extract feed for PA and Warehouse with the exception of the Real Property extracts.  The files will be made available through DAAS GEX.  It is requested the file be created daily.</p> <p><strong>Mission Critical</strong> <br /> Mission Critical as per guidance for Army Vantage program</p> <p><strong>Benefits</strong> <br /> Improves Army Vantage's ability to accomplish the mission</p> <p><strong>Users</strong> <br /> All</p> <p> </p> <p> </p> <p><strong>Completed - Release 2021.2 -- 28 May 2021</strong></p>
20513Ability to add attachments to transfers01649PAAF: GEITNewSubmitted: 23 Nov 2020<p><strong>Description</strong> <br /> Property Administrators are required to attach documentation to each transaction within DPAS. At this time, they are unable to attach supporting documentation when performing transfers.</p> <p><strong>Recommended</strong> <br /> Add the ability to upload attachments to affected asset records which are a part of transfer transactions.</p> <p><strong>Mission Critical</strong> <br /> Yes. Per FIAR/FAR guidance, key supporting documents must be attached to each transaction within the APSR.</p> <p><strong>Benefits</strong> <br /> This change would allow for better tracking of accountability, in that the associated documentation would be directly attached to the transfer transaction.</p> <p><strong>Users</strong> <br /> Yes</p>
20512Incorporate pRFID capability into Individual Issue01648WarehouseLeidosNewSubmitted: 16 November 2020<p><strong>Description</strong> <br /> The DPAS Individual Issue process does not currently support issue by pRFID number. pRFID numbers are unique. By scanning the pRFID that is related to inventory, the issue can be made efficiently and accurately. The DPAS PM has requested that DPAS be able to provide a proof of principle (POP) to the U.S Coast Guard for their cadet clothing issues.</p> <p><strong>Recommended</strong> <br /> The POP will consist primarily of bulk clothing, which could be hundreds/thousands of identical items being received. To support this POP, 1) DPAS will need a method to efficiently capture and associate the pRFIDs with the inventory during the receiving phase, or possibly have a separate pRFID process that could augment receiving, and 2) the goal would be to modify the existing Individual Issue process to enable the scan/capture of the pRFIDs that are attached to the items being issue displaying the Stock Nbr / Qty in the issue process. For the POP, it is not necessary to have DPAS create a process to assign pRFIDs to bulk materiel, or to implement pRFID into the Individual Return process. These modifications would only be needed should issue by pRFID become a core DPAS process.</p> <p><strong>Mission Critical</strong> <br /> This is a DPAS PM requirement.</p> <p><strong>Benefits</strong> <br /> Reduced manpower through automated scans, and improve accuracy</p> <p><strong>Users</strong> <br /> All users who perform Individual Issues and have items tagged with a pRFID</p>
20511Support Local Catalog Stock Numbers within DPAS01647EnterpriseLeidosDoneSubmitted: 11/16/2020<p><strong>Description</strong> <br /> There is a need to catalog local stock numbers outside of the standard NSN, MCN and part number formats.</p> <p><strong>Recommended</strong> <br /> This involves creating a new stock item type code of 'L - LSN' and updating the catalog interface to allow the entry of the stock number - max length 15 characters with the validation:  alphanumeric with supported special characters $, -, /, \#, &, ;, (, ), comma, period, and space.  Impact to DLMS transaction processing will be minimized and addressed.</p> <p><strong>Mission Critical</strong> <br /> mission critical</p> <p><strong>Benefits</strong> <br />Allows DPAS to support individual agency's cataloging policy requirements</p> <p><strong>Users</strong> <br /> all users</p> <p><strong>Completed – Release 2020.3.3 – 4 December 2020</strong></p>
20510GAFS-R Reporting Lever Location01646Materiel ManagementAF: OtherNewSubmitted: 10 Nov 2020<p><strong>Description</strong> <br /> SAF/FM is constraining the CICP go-live dates in DPAS to the first day of a new quarter.  This places pressure on the CICPs, the GFM-A team and the DPAS implementation team into these four days each year.  In consultation with our DPAS support team, we have proposed establishing a transaction pilot period for each new ICP before DPAS enables the financial reporting to GAFS-R.  Currently, the DPAS reporting lever to GAFS-R is located at the Logistics Program level.  We propose lowering that reporting lever to the ICP level in DPAS.  This will enable us to implement new CICPs on any date without impacting financial reporting.  In addition, the GFM-A team needs the ability to change the beginning and ending dates on the reports in the ICP module (CFO Report, OM&S Trial Balance and Accounting Detail Report) to allow users to pull historical data including transactions for audits.</p> <p><strong>Recommended</strong> <br /> The recommended solution is to move the GAFS-R reporting level in the ICP module from the Logistics Program level to the ICP level. ICP Officers within DPAS should be provided an interface that would allow them to turn the GAFS-R Reporting on or off for each ICP under their Logistics Program.  Remove the block from the beginning dates and ending dates from the financial reports in the ICP Module.</p> <p><strong>Mission Critical</strong> <br /> This is critical to the implementation of the 100 AF CICPs; this removes constraints on all teams supporting the CICP implementations in DPAS.  Allows programs to provide transaction sets to auditors.</p> <p><strong>Benefits</strong> <br /> This provides the ability to review CICP transactions for accuracy prior to sending financial data to GAFS-R.  It further provides the opportunity to correct any errors in the transactions.  Provides ability to provide transaction sets for reconciliation and audits.</p> <p><strong>Users</strong> <br /> ALL AF GFM-A users</p>
20509DLA Required Changes for VA PPE Mgmt01645WarehouseDLADoneSubmitted: 05 Nov 2020<p><strong>Description</strong> <br /> DLA is implementing DPAS Warehouse module to support receipt, storage, and issue of the Veterans Administration's PPE. <br /> Currently there is no electronic communication of Requisitions / MROs. <br /> DLA does have a requirement to route the MRO to a TMO to have the materiel shipped (DLMS ADC 316 Functionality). <br /> It appears that the ADC 316 functionality within DPAS only works with external ICPs. <br /> The ADC 316 functionality is between the TMO and Warehouse and should not be dependent upon an ICP being associated to the Warehouse / Owning DoDAAC. <br /> There also appears to be an issue with the printing of Special Instructions. <br /> The allowable characters are insufficient, and it appears they only print when the continuation page is printed which is only printed when the MRO is for serialized assets and the Qty > 1. <br /> Special Instructions should print for all MROs when entered. <br /> The TMO DLMS 945A needs to be reviewed to determine if all of the data is being extracted related to the shipment. <br /> This information needs to be extracted and included in the DLMS 945A to the ICP and 856S to the customer.</p> <p><strong>Recommended</strong></p> <ol> <li>  Review current ADC316 TMO functionality to ensure it functions with all MROs that contain a valid TMO RIC / Transportation Account Code (TAC).</li> <li>  Validate what fields are required to generate a 940R to a TMO.  Add BRs for fields that are currently not marked as required when a TMO is present to make them required.</li> <li>Increase the number of allowed characters for special instructions, and ensure they print when present (either add to main 1348 to the right of block 27, or always print the continuation page when special instructions are present). DLA desires the capability for 4 lines with each line having 25 characters.</li> <li>Review the inbound DLMS 945A to ensure DPAS is extracting all of the shipping elements and including them in the DLMS 945A to the ICP as well as the 856S.</li> </ol> <p><strong>Mission Critical</strong> <br /> Yes. Without this change, DLA will need to delay the implementation of DPAS for managing the Veterans Administration PPE.  Estimated Required Delivery date of this functionality is 12/1/2020.</p> <p><strong>Benefits</strong> <br /> Accurate accounting and reporting for materiel is mandatory.</p> <p><strong>Users</strong> <br /> These changes will improve Warehouse for all users who use this functionality. </p> <p><strong>Completed – Release 2021.1 – 5 February 2021</strong></p>
20508Improve Individual Issue01644WarehouseAF: USAFADoneSubmitted: 05 Nov 2020<p><strong>Description</strong> <br /> USAFA contacted DPAS to seek improvements in the Individual Issue process.  Overall, they are very pleased with what DPAS has provided, but when they have fielding day, they struggle to be able to service all of the cadets in a single day.  That perspective alone, they have identified several items that if DPAS were modified, they believe they would be able to service the cadets.</p> <p><strong>Recommended</strong></p> <ol> <li>Display of Member Profile data at the commencement of the issue.  They are not currently using MILs and believe if they could bypass this step, they could achieve more throughput <ul> <li> Add to the Warehouse AUD a check box (bit_flg) to indicate whether to display the Member Profile upon entering the II process.</li> <li> Modify Individual Issue to read display switch and act accordingly.</li> </ul> </li> <li>Scanning of Bar Codes should increment Qtys.  This would streamline the issue. <ul> <li> Improve the scan feature to support Qty updates.  Either scan will increase Qty or a Scan of a bulk asset will pop up a Qty box for the user to input the qty.</li> </ul> </li> <li>Manual Sign - When the issue is complete, DPAS displays the quick print window.  They do not print a completed from.  They want this not to display to streamline the process and increase the throughput. <ul> <li> Add to the Warehouse AUD a check box (bit_flg) to indicate whether to display the print window. Need to determine at what phase they want to stop the sign/print step. May require more than 1 check box or a drop down of options.</li> <li>Modify Individual Issue to read display switch and act accordingly.</li> </ul> </li> <li>Once they complete an issue and want to start the next issue, they indicated they must select the Back Arrow.  They are looking for a faster / easier to start the next Issue. <ul> <li> Add a "New" Button to Screen to return the user to page 1 of the issue process to start the selection of the next member.</li> </ul> </li>  </ol> <p><strong>Mission Critical</strong> <br /> Critical:  USAFA must process individual  issues to 1000 incoming cadets in a single day.</p> <p><strong>Benefits</strong> <br /> Reduces the Time/Cost of large scale Individual Issues.</p> <p><strong>Users</strong> <br /> All WH users could benefit from the streamlining of the individual issue process outlined above.</p> <p><strong>Completed – Release 2021.1.4 – 30 April 2021</strong></p>
20507Generate DLMS867I For Materiel Release Order01643WarehouseLeidosDoneSubmitted: 11/2/2020<p><strong>Description</strong> <br /> USMC LOGCOM is transitioning from the Air Force Stock Control System (SCS) to Navy Enterprise Resource Planning System (NERP) for inventory management of the wholesale inventory that is managed within DPAS warehouses.  Communication between NERP and DPAS will be DLMS transactions.  With the change in inventory control system, NERP requires the Warehouse system to generate a DLMS 867I (Issue) as part of the Materiel Release Advice shipment report (DLMS 945A).</p> <p><strong>Recommended</strong></p> <ol> <li>Incorporate a flg within the Owning DoDAAC profile to indicate whether the system needs to generate a Issue (867I).</li> <li>Modify LPWNH35 (MRO) to generate a DLMS 867I when flg is true for the Owning DoDAAC.</li> <li>Incorporate business rules provided by NERP/USMC to determine the Product Transfer Type Code (To be provided later).</li> <li>Consideration should be given to adding a flg for the generation of the DLMS 856S transaction as this is currently dedicated to SCS. <br /> NERP will likely require DPAS to generate the DLMS 856S along with other systems as it is not configured to account for materiel at the serial nbr/batch level.</li> <li>Modify LPWHN35 to check for 856S flg.  When present, generate the Shipment Status (DLMS 856S); otherwise, do not generate the Shipment Status.</li> </ol> <p><strong>Mission Critical</strong> <br /> Yes. Without this change, USMC cannot transition to NERP.</p> <p><strong>Benefits</strong> <br /> Provides USMC with a modern Materiel Mgmt system and enable USMC to become compliant with Navy policy</p> <p><strong>Users</strong> <br /> The impact to the user is negligible as this will be limited to background processing with the exception of the setup of the Owning DoDAAC's profile. </p> <p><strong>Completed – Release 2021.1 – 5 February 2021</strong></p>
20506Warehouse Roles Modification01642WarehouseArmy: ASA(ALT)NewSubmitted: 30 Oct 2020<p><strong>Description</strong> <br /> While conducting a annual review the ASA(ALT) DPAS established customized roles, we realized that some roles need more allocations to perform their functions and daily operations. ASA(ALT) proposes giving certain DPAS positions more capabilities by requesting a change to provide them with more control over their process in DPAS.</p> <p><strong>Recommended</strong> <br /> Requesting to modify current ASA ALT DPAS Warehouse user role functionalities to support DPAS work functions.  Attached is the functionality change modification request, highlighted in yellow, and place the functionalities needed in the block. Also attached is the current ASA ALT DPAS Warehouse roles description and functionalities.</p> <p><strong>Mission Critical</strong> <br /> This role improvement will give the users more accessibility to their assets in their prescriptive roles in DPAS aligned to Army internal controls and audit readiness.</p> <p><strong>Benefits</strong> <br /> These changes will give the user more functionality in their roles in DPAS. These changes will help them complete their process promptly. It will also provide the users with the capability to complete every function needed without reaching to higher commands to run any functionality.</p> <p><strong>Users</strong> <br /> Yes it will affect all users within ASA(ALT).</p>
20505ICP Roles Modification01641Materiel ManagementArmy: ASA(ALT)NewSubmitted: 30 Oct 2020<p><strong>Description</strong> <br /> While conducting a annual review the ASA(ALT) DPAS established customized roles, we realized that some roles need more allocations to perform their functions and daily operations. ASA(ALT) proposes giving certain DPAS positions more capabilities by requesting a change to provide them with more control over their process in DPAS.</p> <p><strong>Recommended</strong> <br /> Requesting to modify current ASA ALT DPAS ICP user role functionalities to support DPAS work functions.  Attached is the functionality change modification request, highlighted in yellow, and place the functionalities needed in the block. Also attached is the current ASA ALT DPAS ICP roles description and functionalities.</p> <p><strong>Mission Critical</strong> <br /> This role improvement will give the users more accessibility to their assets in their prescriptive roles in DPAS aligned to Army internal controls and audit readiness.</p> <p><strong>Benefits</strong> <br /> These changes will give the user more functionality in their roles in DPAS. These changes will help them complete their process promptly. It will also provide the users with the capability to complete every function needed without reaching to higher commands to run any functionality.</p> <p><strong>Users</strong> <br /> Yes it will affect all users within ASA(ALT).</p>
20504Tech Refresh - Create Single Page to Enter Help Links for Page Sensitivity01640EnterpriseLeidosNewSubmitted: Tech Refresh - Create Single Page to Enter Help Links for Page Sensitivity<p><strong>Description</strong> <br /> Right now to make the Help page sensitive, there needs to be a link between each page of the DPAS application and the matching Help Topic. To accomplish this, the Technical Writer and developers must create those links within the DPAS application.</p> <p><strong>Recommended</strong> <br /> Create a page where a non-programmer (such as the Technical Writer) can enter the unique Help IDs and have them automatically link to the correct DPAS application pages. (If a identifier is necessary for the DPAS page, make it something like the CI or something easily found.)</p> <p><strong>Mission Critical</strong> <br /> It is necessary for the help to be linked properly to the DPAS application in a timely manner.</p> <p><strong>Benefits</strong> <br /> Reduces time, improves effectiveness.</p> <p><strong>Users</strong> <br /> Technical Writers, All Developers within DPAS.</p>
20502Lock down adding ability to Attributes for Warehouse Officer only01639WarehouseAF: AFERMSDoneSumbitted: 9 Oct 2020<p><strong>Description</strong> <br /> Need to lock down the ability to group name; attribute name and type under the members Attributes under member profile. This should only be able to edited by Warehouse officer. Currently Warehouse technician can edit and add new.</p> <p><strong>Recommended</strong> <br /> Under Member Profile, under Member Attributes lock down ability to add any new group names or attribute names.</p> <p><strong>Mission Critical</strong> <br /> YES! Warehouse technicians are adding all types of information, spelling wrong, wrong kind of sizes, so when we run reports we have all kinds of misinformation for sizes.</p> <p><strong>Benefits</strong> <br /> data accuracy.</p> <p><strong>Users</strong> <br /> All</p> <p><strong>Completed – Release 2021.1 – 5 February 2021</strong></p>
20501Incorporate pRFID capability into Individual Issue01638WarehouseLeidosNewSubmitted: 9 October 2020<p><strong>Description</strong> <br /> The DPAS Individual Issue process does not currently support issue by pRFID number.  pRFID numbers are unique.  By scanning the pRFID that is related to inventory, the issue can be made efficiently and accurately.  The DPAS PM has requested that DPAS be able to provide a proof of principle (POP) to the U.S Coast Guard for their cadet clothing issues.</p> <p><strong>Recommended</strong> <br /> The POP will consist primarily of bulk clothing, which could be hundreds/thousands of identical items being received. To support this POP:</p> <ul> <li>DPAS will need a method to efficiently capture and associate the pRFIDs with the inventory during the receiving phase, or possibly have a separate pRFID process that could augment receiving.</li> <li>the goal would be to modify the existing Individual Issue process to enable the scan/capture of the pRFIDs that are attached to the items being issue displaying the Stock Nbr / Qty in the issue process.</li> </ul> <p>For the POP, it is not necessary to have DPAS create a process to assign pRFIDs to bulk materiel, or to implement pRFID into the Individual Return process. These modifications would only be needed should issue by pRFID become a core DPAS process.</p> <p><strong>Mission Critical</strong> <br /> This is a DPAS PM requirement.</p> <p><strong>Benefits</strong> <br /> Reduced manpower through automated scans, and improve accuracy.</p> <p><strong>Users</strong> <br /> All users who perform Individual Issues and have items tagged with a pRFID.</p>
20500Reconstitute Planned Pick for HHT01637WarehouseLeidosNewSubmitted: 9 October 2020<p><strong>Description</strong> <br /> The initial fielding of the DPAS warehouse module included Planned Picking on a HHT.  With the sunset of the original HHTs, there is a requirement to reconstitute the Planned Pick process in a disconnected mode that functions with the currently supported DPAS AIT.</p> <p><strong>Recommended</strong> <br /> Provide the capability to view, pick and deliver planned picks via an AIT terminal that is compatible with DPAS. The solution will be able to export planned picks for disconnected operation, and be able to import them when the terminal is reconnected.  All of the business processes related to confirming the pick is to be completed by this SCR to include updating the MRO to Picked/Ready for Release and generate a QC action when applicable.  When operating connected, the process should receive new picks and post completed picks real-time.</p> <p><strong>Mission Critical</strong> <br /> Yes.  Reconstitution of existing functionality for use with currently approved AIT devices.</p> <p><strong>Benefits</strong> <br /> Reduced manpower through automated scans, and improve accuracy.</p> <p><strong>Users</strong> <br /> All users who utilize the planned pick process.</p>
20499DPAS Tech Refresh - Background Process Manager / Pendulum (Job Scheduler)01636EnterpriseLeidosNewSubmitted: 10/1/2020<p><strong>Description</strong> <br /> Provide single point, end user capability for managing/scheduling jobs as well as to receive critical production feedback on issues for analysis and resolution.</p> <p><strong>Recommended</strong> <br /> The initial focus will be operations based – triage, research, issue identification and resolution.  Additional functionality will be submitted for monitoring and possible trend analysis in the form of a configurable dashboard.</p> <p><strong>Mission Critical</strong> <br /> This was mandated as a requirement of Tech Refresh.</p> <p><strong>Benefits</strong></p> <ul> <li>improved production support capability</li> <li>improved visibility to system and application status</li> <li>improved research, triage and error identification tools</li> </ul> <p><strong>Users</strong> <br /> Prod Support Team</p>
20498DPAS Tech Refresh - Common Asset Model01635EnterpriseLeidosNewSubmitted: 10/1/2020<p><strong>Description</strong> <br /> Establish a DPAS common asset model to support the DPAS Tech refresh work effort.</p> <p><strong>Recommended</strong> <br /> DPAS will provide a centralized asset structure that is accessible to all DPAS processes and platforms. <br /> This structure will contain a core set of attributes that are common to all DoD business processes.  <br /> Process specific attributes will extended off of the Common Asset structure in a "hub and spoke" model. <br /> The Common Asset structure will provide an enterprise wide method to uniquely identify each asset in DPAS and share those common attributes throughout the system. <br /> Microservice API(s) will be established, use-able by all development teams to insert assets into the new asset structure.  <br /> This SCR requires that the Common Asset structure support both the new model and the existing, disparate asset models in DPAS today. <br /> The Common Asset structure should maintain an in-sync balance between old and new models until all processes have transitioned to the new Common Asset structure. <br /> Reports and monitoring will be provided to monitor/ensure balance between the asset model and the legacy DPAS application as organizations/DPAS transitions to the tech refresh framework.</p> <p><strong>Mission Critical</strong> <br /> This was mandated as a requirement of Tech Refresh.</p> <p><strong>Benefits</strong> <br /> The separation of the common asset attributes and the extension tables by specific platform provides a more efficient application design which limits risk by isolating changes to the asset model to specific platforms and its related asset attributes.  <br /> Provides full visibility of the full life cycle of the asset, regardless of activity or platform.</p> <p><strong>Users</strong> <br /> All</p>
20497DPAS M&U Tech Refresh01634MULeidosIn ProgressSubmitted: 29 Sept 2020<p><strong>Description</strong> <br /> Update Maintenance and Utilization functionality to support the DPAS Tech refresh work effort.</p> <p><strong>Recommended</strong></p> <ul> <li>Update the GUI to have a more modernized look</li> <li>Update the back end to increase speed and user performance</li> </ul> <p><strong>Mission Critical</strong> <br />N/A</p> <p><strong>Benefits</strong> <br /> Improved Customer experience for all DPAS Users</p> <p><strong>Users</strong> <br /> ALL</p> <p> </p> <p> </p> <p> </p> <p> </p> <p> </p> <p><strong> Partially completed -- Release 2021.2 - 28 May 2021</strong></p> <p><strong> Partially completed -- Release 2021.3 - 10 Sept 2021</strong></p>
20496DPAS Tech Refresh Catalog01633EnterpriseLeidosIn ProgressSunbmitted: 29 Sept 2020<p><strong>Description</strong> <br /> Update the DPAS Catalog functionality to support the DPAS Tech Refresh work effort.</p> <p><strong>Recommended</strong> <br /> DPAS will provide a centralized Catalog that is accessible for all DPAS processes and assets. The DPAS Catalog will provide a core set of attributes that are common to all features with extendable attributes sets that are required for specific platform and their features.</p> <p><strong>Mission Critical</strong> <br /> N/A</p> <p><strong>Benefits</strong> <br /> Improved customer experience for all DPAS Users.</p> <p><strong>Users</strong> <br /> All</p> <p><strong> Partially Completed -- Release 2021.2 - 28 May 2021</strong></p>
20495PA DLMS 856S/527D Changes01632EnterpriseLeidosDoneSubmitted: 09/10/2020<p><strong>Description:</strong> <br /> When the 527D/856S DLMS process was added into PA, the MILS fields were hard-coded. AFSOC needs us to change how this process works to allow users to select values for those hard-coded fields, as well as make the RIC fields optional. Additionally, we need to fix the 527D/856S process to inbound correctly to the Warehouse module via the DLMS processor.</p> <p><strong>Recommended:</strong> <br /> In PA, when the 527D/856S DLMS process is executed as Disposition>Transfer Out-Outside DPAS, the MILS fields should be available for users to select values, as well as make the RIC fields optional for the "from" and "to" addresses. <br /> Also, fix the 527D/856S process to inbound correctly to the Warehouse module via the DLMS processor, and fix the UIC DoDAAC/CAGE add/delete process to allow for DLMS fields to be added/changed when a DoDAAC/CAGE is re-added after it's been deleted.</p> <p><strong>Mission Critical:</strong> <br /> Required by AFSOC</p> <p><strong>Benefits:</strong> <br /> Improves the function of these DLMS processes out of PA</p> <p><strong>Users:</strong> <br /> Certain users who utilize DLMS transactions out of PA Disposition</p> <p><strong>Completed – Release 2020.3.1 – 23 October 2020</strong></p>
20494Nuclear, Reimbursable, Mission Critical Indicator01631MUAF: VSCOSNewSubmitted: 8 September 2020<p><strong>Description</strong> <br /> DPAS does not identify an asset as nuclear certified, reimbursable or mission critical when opening a work order. Fleet analysts and technicians need a simple, standard and repeatable solution to distinguish nuclear certified, reimbursable or mission critical assets to properly manage, direct actions or perform maintenance.</p> <p><strong>Recommended</strong> <br /> Create Nuclear indicator (NCE), nuclear restricted indicator (NCE-R) and nuclear restricted remarks (i.e., Restricted Remarks) fields to reflect an asset as nuclear certified in 3 locations; the Custodian Asset Report (inventory), the MAM in M&U and on the asset work order (electronic and/or print). <br /> Add checkbox in the "fields" section of both PA and M&U inquiries allowing queries and quick identification of nuclear certified assets. <br /> Ideally, load the nuclear indicator against the NSN at the catalog level with a field indicating "NCE". <br /> However, the Air Force requires editing field because assets within a specific NSN become restricted and the ability to remove the NCE designator from a specific asset, switching to NCE-R. <br /> Recommend accompanying the NCE-R designator field with a "restricted comments box" with enough free text characters to easily input why restriction exists on a nuclear asset. <br /> Additionally, add two additional fields identifying Reimbursable and Mission Critical assets. <br /> Recommend drop down field selections with A/U/D on the MAM. Locate the fields on the Basic tab. <br /> Name the Fields and drop down selections: "Remb/Refd" with provisions to choose either "3" for reimbursable or "4" for refundable" and "Msn Crt" displays a "C" for mission critical. <br /> Blank Fields for the conditions not applicable. <br /> The field names Remb/Refd and Msn Crt must reflect on the basic work order (electronic and print) when processing a work order. <br /> Additionally, all fields (to include cost centers) must be easily identifiable when pulling a Maint Asset inquiry or a work order/sub work order inquiry. </p> <p><strong>Mission Critical</strong> <br /> Critical.  It is imperative Air Force managers and technicians know a nuclear certified asset's certification to handle special cargo.  Nuclear certified assets follow additional rules governing maintenance; requiring the technician an easily identifiable indicator on the work order for compliance with AFI 63-125, Nuclear Certification Program.  Furthermore, it is imperative an easily identifiable indicator and inquiry for refundable or reimbursable assets   to manage sustainment funds as well as the ability to easily identify mission critical assets per AFI 24-302, Vehicle Management.</p> <p><strong>Benefits</strong> <br /> Benefits of implementing change includes safety and movement of special weapons, proper accountability of nuclear support equipment mission sets, saving research time opening a work orders, potential improper maintenance actions on nuclear surety assets, and proper visual restriction of nuclear certified status.  Additionally, save time identifying refundable and reimbursable assets as well as improve accuracy of financial reporting.</p> <p><strong>Users</strong> <br /> All Air Force asset managers (i.e., vehicles and equipment) utilize this information for day-to-day management purposes.</p>
20493Include Safety Stock % in LPWHR82 - Inventory Over Under Report Calculation01630WarehouseAF: AFERMSDoneSubmitted: 18 AUG 2020<p><strong>Description </strong> <br /> LPWHR82 - Inventory Over Under Report - does not include the safety stock percentage into stock number calculation</p> <p><strong>Recommended </strong> <br /> Update Inventory Over/Under Report LPWHR82 to incorporate MIN/MAX safety stock percentage into stock number calculation.</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong> <br /> accuracy of report information</p> <p><strong>Users</strong> <br /> ALL AFERMS</p> <p><strong>Completed – Release 2021.1.1 – 26 February 2021</strong></p>
20492MAINTENANCE ASSET UTILIZATION INQUIRY REPORT FOR DPAS - RRAD INQUIRY AND RFI01629MUArmyNewSubmitted: 18 Aug 2020<p><strong>Description</strong> <br /> There is no way to divide the equipment out when running utilization report. By adding office id to this report we could sort by Cost Centers. RRAD Equip Control Clerk, Jose Arredondo (903-334-2115) asks, "Can the "Office ID" option found in the Dispatch Inquiry report be made available in the Maint Asset Utilization Inquiry report?"</p> <p><strong>Recommended</strong> <br /> To add office ID (Cost Center) to utilization reports. RRAD states: "I am needing this information on the Maint Asset Utilization Inquiry report in order to separate or sort by Office ID."</p> <p><strong>Mission Critical</strong> <br /> This is a critical to reporting to the users and the management for the depot to right size the fleet at RRAD. TACOM (MSC) concurs based on site visits for the Command Inspection Program that this would be very beneficial to their organization and for our analysis.</p> <p><strong>Benefits</strong> <br /> Reduces time to look up each vehicle. With this added field we would be able to sort by office ID(Cost Center). As well, there becomes an ability to better manage fleet utilization. Again, as well, the MSC can track the subordinate organization for cost effectiveness in fleet management during VAM and CIP.</p> <p><strong>Users</strong> <br /> This affects all users.</p>
20491DoDAAC01628PAAF: AFEMSNewSubmitted: 10 Jul 2020<p><strong>Description</strong> <br /> When processing a Disposition or Transfer with the DAAS interface on the document number needs to change to reflect the gaining UICs DODAAC. </p> <p><strong>Recommended</strong> <br /> When assigning the document number automatically default to the gaining DODAAC when interface is on.</p> <p><strong>Mission Critical</strong> <br /> Mandated by system, error occurs if DODAAC in the document number isn't changed.</p> <p><strong>Benefits</strong> <br /> Reduces time</p> <p><strong>Users</strong> <br /> yes</p>
20490Mass UIC to UIC01627PAAF: AFEMSNewSubmitted: 10 Jul 2020<p><strong>Description</strong> <br /> Property records on an existing UIC require a mass UIC to UIC transfer when a unit is re-designated and a new UIC is established.</p> <p><strong>Recommended</strong> <br />Propose that the system internally updates the master data file to reference the original UIC and move all custodian records to the new UIC.</p> <p><strong>Mission Critical</strong> <br /> Mission critical, as a unit designation changes, the property records need to be reported against the correct UIC.</p> <p><strong>Benefits</strong> <br /> Improves accountability and accuracy</p> <p><strong>Users</strong> <br /> yes</p>
20489FSM Inquiries Issue01626FSMAF: AFEMSNewSubmitted: 10 Jul 2020<p><strong>Description</strong> <br /> The FSM Inquiries/Authorization Review Inquiry results should match the template of the Utilities/File Upload feature by default. Currently, inquiry results lack data fields for Platform Description, Authorization Match Quantity Flag, Authorization Unit Edit Flag, Date Last Reviewed, Reviewer and Organization Match Quantity.  Also, the inquiry data is not organized in the same order as the Utilities/File Upload template.</p> <p><strong>Recommended</strong> <br /> Update the FSM Inquiries/Authorization Review Inquiry screen to match the FSM Utilities/File Upload template by default. The other data fields currently in the Authorization Review Inquiry should remain as viewable and down-loadable for the user.</p> <p><strong>Mission Critical</strong> <br /> Mission Critical:  As Authorization Managers work to reorganize imported data as necessary to conform to new Force System Management criteria, this enhancement is essential to data integrity.</p> <p><strong>Benefits</strong> <br /> Benefits user by reducing amount of time creating/organizing downloaded data to match the File Upload template.  Also reduces chance of human error in regards to data entries.</p> <p><strong>Users</strong> <br /> All FSM and Authorization Managers</p>
20488FSM Data Query 0301625FSMAF: AFEMSNewSubmitted: 10 Jul 2020<p><strong>Description</strong> <br /> The inability to scroll left or right through data query results when viewing the top or middle records. The left/right scroll bar is only found at the bottom the data query results.</p> <p><strong>Recommended</strong> <br /> Create a floating left/right scroll bar that remains visible at the bottom of the screen while browsing through the entire query.</p> <p><strong>Mission Critical</strong><br /> N/A</p> <p><strong>Benefits</strong> <br />Benefits user by reducing amount of time taken to review data results.  Reduces research and processing times by providing the ability to scroll though entire data field without having to continually drop to bottom of query. </p> <p><strong>Users</strong> <br /> All</p>
20487FSM Data Query 0201624FSMAF: AFEMSNewSubmitted: 10 Jul 2020<p><strong>Description</strong> <br /> In any FSM data query function, the inability to identify column headings while browsing through numerous records results in the user having to track back to the beginning of the inquiry to confirm targeted data fields.</p> <p><strong>Recommended</strong> <br /> Create floating column headings that remain visible as the user browses though data records.</p> <p><strong>Mission Critical</strong> <br /> This is critical since an update to the wrong data column could occur.  The enhancement will also save valuable processing time.</p> <p><strong>Benefits</strong> <br /> It benefits the user by reducing the amount of time exploring data results by not having to return to the top of the data screen to verify column headings. It also ensures data integrity by ensuring the user is updating the correct data field.</p> <p><strong>Users</strong> <br /> All</p>
20486FSM Mass Update01623FSMAF: AFEMSNewSubmitted: 10 Jul 2020<p><strong>Description</strong> <br /> Inability for mass updates to OReq and OAuth data fields.</p> <p><strong>Recommended:</strong> <br /> Allow users the capability to perform mass updates to OReq and OAuth data fields.</p> <p><strong>Mission Critical</strong> <br /> This is critical due to the nature of how Air Force manages mobility authorizations.  Changes to the Authorization Detail during UTC reviews could result in hundreds or thousands of needed changes to OReq and OAuth data fields.</p> <p><strong>Benefits</strong> <br /> Mass updates are required to alleviate labor intensive process of updating OReq and OAuth fields manually.</p> <p><strong>Users</strong> <br /> This change will affect all users within our SiteID.</p>
20485Check-In KIOSK01622WarehouseUSMC: CSPDoneSubmitted: 10 July 2020<p><strong>Description</strong> <br /> Currently the current 3PL operates 8 SLIM KIOSK which are located throughout 8 of are larger IIF's this KIOSK is used to help track member's coming into the warehouse facility, when they came into the warehouse and how long they had to wait before there service time began.  Members are then put in a staging cue until it is time for that member to be serviced.</p> <p><strong>Recommended</strong> <br /> Recommending that DLA or Leidos develop a check-in KIOSK that interfaces with the DPAS-WM.  Below are some of the minimum requirements:</p> <ul> <li>Free Standing Kiosk Kit with PC and built-in CAC Scanner. </li> <li>Hardware/Software Support and Maintenance for ATO Accredited System ACF.</li> <li>Wireless Printing Capability</li> <li>Customer Queue Routing</li> <li>Customer Call-Back</li> <li>Throughput total capture/reporting capability</li> <li>Deployable to multiple current and future CSP warehouse locations</li> <li>Operable on the MCEN</li> <li>Capable of operating through alternate wifi networks, such as through mobile hotspot</li> </ul> <p><strong>Mission Critical</strong> <br /> Customer wait times is a very high visibility requirement that is looked at on a daily basis. Monitoring customer wait times is an important part of CSP's Quality Assurance Surveillance Plan and is used to address resource optimization in day to day operations. </p> <p><strong>Benefits</strong> <br /> Having this type of solution will give us the ability to monitor customer wait times and also how many members are in line.  With this type of information we are able to triage the situation and make the best recommendations to lower the wait time and get members serviced faster.</p> <p><strong>Users</strong> <br /> All IIF & UIF</p> <p><strong>Completed – Release 2021.1 – 5 February 2021</strong></p>
20484Real Property - CIP01621PAUSMC: MCCSNewSubmitted: 7/8/2020<p><strong>Description</strong> <br /> CIP <br />                Add data elements required for USMC MCCS Real Property <br />                Import expense data</p> <p><strong>Recommended</strong> <br /> CIP <br />                Add data elements required for USMC MCCS Real Property <br />                Import expense data</p> <p><strong>Mission Critical</strong> </p> <p><strong>Benefits</strong> </p> <p><strong>Users</strong> <br /> ALL</p>
20483Real Property01620PAUSMC: MCCSDoneSubmitted: 7/8/2020<p><strong>Description</strong> <br /> 1) Real Property – Add data elements to complete the required elements for tracking their Real Property.  The known data elements are below.   There may be more identified after the MCCS personnel review currently available fields. <br /> i. Interior Condition Code <br /> ii. 5 Dollar Fields for FY, FY+1, FY+2, FY+3, FY+4</p> <p><strong>Recommended</strong> <br /> 1) Real Property – Add data elements to complete the required elements for tracking their Real Property.  The known data elements are below.   There may be more identified after the MCCS personnel review currently available fields. <br /> i. Interior Condition Code <br /> ii. 5 Dollar Fields for FY, FY+1, FY+2, FY+3, FY+4</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong></p> <p><strong>Users</strong> <br /> ALL</p> <p>Linked to <a href="index.php/support/system-change-request/details/4/20448/usmc-naf-real-property-enhancements?start=0">SCR #01585</a></p> <p><strong>Completed – Release 2020.3.2 – 13 November 2020</strong></p>
20482CIP Project - Project Planning01619PAUSMC: MCCSIn ProgressSubmitted: 7/8/2020<p><strong>Description</strong> <br /> 1) Project Planning<br />a. Add tab/data elements to complete the elements required to track the Projects <br /> i. Track Requested/Reviewed/Rejected/Approved/Create CIP Project</p> <p><strong>Recommended</strong> <br /> 1) Project Planning<br />a. Add tab/data elements to complete the elements required to track the Projects <br /> i. Track Requested/Reviewed/Rejected/Approved/Create CIP Project</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong></p> <p><strong>Users</strong> <br /> ALL</p> <p><strong>Partially Completed - Release 2021.3 - 10 Sept 2021</strong></p>
20481ASA(ALT) Role Updates01618WarehouseASA(ALT)NewSubmitted: 6/24/2020<p><strong>Description</strong> <br /> Three (3) roles do not have the SKO Assembly function: ALT-Warehouse Officer, ALT-Warehouse Administrator Government, and ALT-Warehouse Administrator Contractor. <br /> I also checked the ICP and compared it to PM AMSA to see if it was set up and from what I understand, it is not.</p> <p><strong>Recommended</strong> <br /> Update 3 Roles to include SKO Assemble.</p> <p><strong>Mission Critical</strong> <br /> Yes.</p> <p><strong>Benefits</strong> <br />  </p> <p><strong>Users</strong> <br /> All</p>
20480Catalog Message01617EnterpriseArmy: ASA(ALT)NewSubmitted: 06/10/2020<p><strong>Description</strong> <br /> AESIP processes for designating stock numbers as serialized too lengthy to keep up with needed cataloging.  This results in stock numbers cataloged with management codes requiring adjustment that cannot be done by customer.  Propose messaging to inform customer AESIP update failed and mechanism for changing management codes.</p> <p><strong>Recommended</strong> <br /> Request that the DPAS customer receive a message when an AESIP update to a management code is not applied automatically.  Message would include the stock number in question and the reason the update did not occur.  Further request customer tool in DPAS for changing the management code after assets already attached.</p> <p><strong>Mission Critical</strong> <br /> This is mission critical for audit and transparency.</p> <p><strong>Benefits</strong> <br /> Adding the modifications would improve accuracy and accountability aligned to audit.  This would streamline items affecting Army logistics’ business processes.  Waiting until DPAS personnel can change management codes through help desk ticket requests anticipated to be onerous due to backlog of AESIP serialization request queue.</p> <p><strong>Users</strong> <br /> Yes</p>
20479Provide Visibility of USCG Exchange Inventory01616PADLADoneSubmitted: 6/8/2020<p><strong>Description</strong> <br /> The U.S. Coast Guard (USCG) is migrating some of its logistics processes to DPAS.  One of those processes is 2 warehouses that hold USCG uniforms.  The uniforms are distributed / sold through the U.S Coast Guard Exchanges.  To support asset visibility, the USCG is requesting that DPAS provide visibility of the uniform inventory held by the exchanges.</p> <p><strong>Recommended</strong> <br /> Modify the DPAS to inbound USCG Exchange uniform inventory and provide a view of the inventory.  Phase 1 will be an overlay type file that contains the inventory by Exchange and Stock Nbr.  For Phase 2 (separate SCR), the Exchanges will provide; Receipts, Issues and Inventory Adjustments by Stock Nbr and Store to enable Demand Planning.  The files would be provided to DPAS via DAAS GEX.</p> <p><strong>Mission Critical</strong> <br /> The USCG has indicated that the visibility of the uniform inventory is a must.</p> <p><strong>Benefits</strong> <br /> Improves the management of the USCG uniforms, which ensures the correct qtys are on hand to prevent shortages and overages.</p> <p><strong>Users</strong> <br /> The change is currently limited to benefiting the USCG.  It may assist others that may require similar functionality (Import  and provide visibility of inventory from external sources).</p> <p><strong>Completed – Release 2020.3 – 9 October 2020</strong></p>
20478ICP Roles Request01615Materiel ManagementArmy: ASA(ALT)DoneSubmitted: 06/05/2020<p><strong>Description</strong> <br /> ASA(ALT) community would like to customize roles for its users in support of the mission objectives of the Program Managers.</p> <p><strong>Recommended</strong> <br /> Modify the DPAS ICP roles to custom ALT roles in support of Army business process; create the ALT roles on the attached spreadsheet aligned to business functions required.</p> <p><strong>Mission Critical</strong> <br /> This is mission critical because ASA(ALT) PMs operate in a slightly different manner than a traditional warehouse.  We also need to have super users available to support each organization.</p> <p><strong>Benefits</strong> <br /> ASA(ALT) PMs will be able to utilize and execute DPAS in accordance with their mission objectives.</p> <p><strong>Users</strong></p> <p><strong>Completed – Release 2020.2.2 – 31 July 2020</strong></p>
20477Process GFP Returns for Non-Serialized UII assets01614PADLANewSubmitted: 02 June 2020<p><strong>Description</strong> <br /> DPAS is not currently receiving Loan Returns from PIEE.  With Release 2020.2 development effort coming to a close, the changes needed to support this on DPAS is not fully known. This SCR is to support the development effort once PIEE corrects their deficiency.  DPAS has also identified a deficiency when multiple serial numbers are included within a single transaction loop within the XML.  This will also need to be resolved.</p> <p><strong>Recommended</strong> <br /> Modify DPAS to locate the assets that are being returned.  This is a change that was not previously implemented when the previous software support provider did not implement.  With PIEE implementing their GFP module, their system is not functioning as it should, thus DPAS will need to receive test transaction to ensure the changes have been applied.  This SCR will require joint testing to insure the assets can be identified as a GFP return.  The return process also needs to be updated to support the new product type codes introduced in ECP 1138, and resolve the deficiency currently preventing the processing of multiple serial numbers within an XML transaction loop.</p> <p><strong>Mission Critical</strong> <br /> DPAS needs to make several changes to support the return of assets to enable DPAS to properly reflect them in the Pending Transaction table as a return.  These are changes that were identified as being missed when the prior DPAS Support provider made the change to support assets.  There is currently a problem that PIEE is working to send these transactions to DPAS.  It is not currently functioning on their end, thus DPAS is not able to make the changes and test  at this time.</p> <p><strong>Benefits</strong> <br /> Eliminates WAWF TS errors and enables the user to view GFP returns once PIEE corrects their deficiency.</p> <p><strong>Users</strong> <br /> This is impacting all DPAS users trying to transmit WAWF GFP TS transactions.</p>
20476Provide for the conversion of CAP to GFP01613PADLANewSubmitted: 02 June 2020<p><strong>Description</strong> <br /> The PIEE GFP module has the capability for the contractor to unilaterally receipt GFP which results in the government system receiving a 856 PSN Receipt notice. The use of this action would be the conversion of CAP to GFP.  Currently DPAS is not able to process this type of PIEE 856 PSN.</p> <p><strong>Recommended</strong> <br /> Modify the WAWF Inbound processes to enable DPAS to create a Pending Receipt for a CAP to GFP conversion.  The Pending Receipt, when processed would place the item under property book control and show it as Out on Loan to the contractor having all of the fields populated as if the government initiated the loan.  This functionality needs to support, UII, Serialized Non-UII, and Bulk assets.</p> <p><strong>Mission Critical</strong> <br /> This is considered mission critical as many of the DPAS Customer have contractors who purchase CAP that eventually will be converted to GFP.  When this occurs, DPAS is not able to successfully process these inbound transactions.</p> <p><strong>Benefits</strong> <br /> Provides for better control of GFP, streamlines the receipt of CAP to GFP conversion assets by the government whereas the government may not have the information needed to receipt for the materiel easily.  It is recommended that DPAS and PIEE work closely to improve the data contained within the 856 PSN.  Attributes such as Acquisition Date and Acquisition Cost are considered critical data elements that  the file does not currently contain.</p> <p><strong>Users</strong> <br /> This is impacting all DPAS users attempting to manage CAP to GFP materiel in DPAS.</p>
20475Provide for Contract Nbr Change for GFP Contracts via PIEE Interface01612PADLANewSubmitted: 02 June 2020<p><strong>Description</strong> <br /> The PIEE GFP module has the capability for the contractor to update the Contract Nbr for the materiel it has as GFP. This is a result of a Follow-On contract award with the materiel remaining with the contractor.  DPAS is not able to process these transactions.</p> <p><strong>Recommended</strong> <br /> Modify the WAWF Inbound processes to support a change in the Contract Nbr to support Follow-on Contracts.</p> <p><strong>Mission Critical</strong> <br /> This is considered mission critical as many of the DPAS Customers have GFP contracts that awarded to the same Vendor for follow-on work.</p> <p><strong>Benefits</strong> <br /> Provides for better control of GFP, prevents DPAS having errors in its PIEE inbound processing of PSN 856 transactions that are not supported.</p> <p><strong>Users</strong> <br /> This change impacts all Customers with GFP contracts.</p>
20474Provide for the management of Bulk GFP Mgmt01611PADLANewSubmitted: 02 June 2020<p><strong>Description</strong> <br /> DPAS does not currently support the issue of Bulk (Non-Serialized) GFP.  With the addition of new customers, there is now a need to be able to issue Bulk materiel to a contractor and to be able to manage that materiel while with the Contractor.  The system must also provide for the return of the bulk materiel, or portions there of where the contractor uses some of the materiel in their testing / manufacturing process.</p> <p><strong>Recommended</strong> <br /> Modify the DPAS Loan process to provide for the capability to assign Bulk items out on loan.  The system must be able to capture and update the receipt acknowledgment of the materiel by the contractor and also provide for the return of the materiel when the contractor no longer has a use for the GFP.  When the government and contractor is connected to PIEE GFP, DPAS should generate and send 856 PSN transaction to GEX for the Issue and be able to accept the 856 PSN for the receipt acknowledgment and the return of the GFP.  When GFP is not returned, DPAS needs to provide a disposition process for it.</p> <p><strong>Mission Critical</strong> <br /> Yes. With the expanded customer base, there is now a need to be able manage and report Bulk GFP.</p> <p><strong>Benefits</strong> <br /> Improvements to Accuracy, Accountability, Financial Reporting.</p> <p><strong>Users</strong> <br /> This is impacting all DPAS customers that have bulk materiel they need to identify and report as GFP.</p>
20473Physical Inventory Count 001610WarehouseNavyDoneSubmitted: 5/29/2020<p><strong>Description</strong> <br /> Physical Inventory: If an asset is unaccounted for during an inventory event, DPAS requires you to enter a qty of ‘0” and records that as the date of last inventory. If the asset is unaccounted for, it should not update the date of last inventory. Ideally, modify DPAS so we are not forced to enter a ‘0’ if an asset is unaccounted.</p> <p><strong>Recommended</strong> <br /> Physical Inventory: If an asset is unaccounted for during an inventory event, DPAS requires you to enter a qty of ‘0” and records that as the date of last inventory. If the asset is unaccounted for, it should not update the date of last inventory. Ideally, modify DPAS so we are not forced to enter a ‘0’ if an asset is unaccounted.</p> <p><strong>Mission Critical</strong> <br /> N/A</p> <p><strong>Benefits</strong> <br /> Improve accuracy of inventories.</p> <p><strong>Users</strong> <br /> All</p> <p><strong>Completed – Release 2021.1.1 – 26 February 2021</strong></p>
20472Generate Multiple Inv Locations At Once01609WarehouseLeidosIn ProgressSubmitted: 5/29/2020<p><strong>Description</strong> <br /> Generate Multiple Inv Locations At Once: Simplify the process. Inventory is conducted every month by location. Each armory has at least 140 locations to generate an inventory event for. Need ability to generate inventory events for multiple locations in a single action.</p> <p><strong>Recommended</strong> <br /> Allow to generate multiple inventory locations at once</p> <p><strong>Mission Critical</strong> <br /> N/A</p> <p><strong>Benefits</strong> <br /> Reduces time needed to generate inventories.</p> <p><strong>Users</strong> <br /> All</p> <p><strong>Partially Completed - Release 2021.3 - 10 Sept 2021</strong></p>
20471GEIT WAWF Activation01608PAAF: GEITNewSubmitted: 28 MAY 2020<p><strong>Description</strong> <br /> Activation of WAWF for AF/GE-IT to receive automated Property System Notices (PSNs) generated by WAWF for receipts and equipment transfers with UIIs. <br /> Currently, GE-IT does not have this functionality activated. <br /> Goal is to establish interface with GSA and AFWAY.</p> <p><strong>Recommended</strong> <br /> Activate/deploy WAWF for GE-IT instance in DPAS, establish connectivity to GSA and AFWAY.</p> <p><strong>Mission Critical</strong> <br /> Yes, this function is mission critical and a requirement driven by AF FIAR 2018.</p> <p><strong>Benefits</strong> <br /> Implementation would provide significant time and cost savings over current manual input or data. <br /> Additionally, would eliminate erroneous data entry through automation.</p> <p><strong>Users</strong> <br /> Activation, with connectivity established between GSA, AFWAY and DPAS would affect site wide inventory.</p>
20470Major Command Code update from PA AUIC/UIC AUD Page01607PALeidosNewSubmitted: 5/27/2020<p><strong>Description</strong> <br /> Upon initial conversion the customer often misses the verification of the Major Command Code of the new UIC.  When this happens, they have no way to update the Major Command Code themselves and submit a Data Update Request to DPAS Support for a SQL script to make the change.</p> <p><strong>Recommended</strong> <br /> Especially in the case of a new UIC (that has no Assets) allow the user to update the Major Command Code from the AUIC/UIC AUD page.</p> <p><strong>Mission Critical</strong> <br /> N/A</p> <p><strong>Benefits</strong> <br /> Reduce data update requests which decrease team efficiency by causing unnecessary work.</p> <p><strong>Users</strong> <br /> Prevents use of new UICs due to invalid settings and the necessity to wait for a SQL Script fix from Leidos.</p>
2046901606 - FAST 2020 Changes01606MULeidosDoneSubmitted: 27 May 2020<p><strong>Description</strong> <br /> Update DPAS MU FAST Reporting for 2020 Report out changes.</p> <p><strong>Recommended</strong></p> <ol> <li>Remove EO 13693 from FAST Outbound Report and display.  Deprecate within MAM locking drop down and prep for tech refresh. </li> <li>Update FAST Manufactures</li> <li>Update FAST vehicle types and FAST vehicle grouping. </li> <li>Update ER and LM association within Vehicle characteristics. </li> </ol> <p><strong>Mission Critical</strong> <br /> Yes for FY20 reporting Sept 2020.</p> <p><strong>Benefits</strong> <br /> FAST DOE compliant. </p> <p><strong>Users</strong> <br /> All</p> <p><strong>Completed – Release 2020.2.1 – 10 July 2020</strong></p>
20468ASA ALT Roles Modification01605WarehouseArmy: ASA(ALT)DoneSubmitted: 23 Apr 20<p><strong>Description</strong> <br /> ASA(ALT) community would like to update our customize roles for its users in support the new mobile inventory capability under AIT Management.</p> <p><strong>Recommended</strong> <br /> Provide the “Physical Inventory – Mobile Device” and “Physical Inventory and Resolution – Mobile Device” functions (AIT Mgmt) to the following ALT Roles highlighted in the AIT Mgmt Request spreadsheet attached (reference Encl 1 attachment).</p> <p><strong>Mission Critical</strong> <br /> This is mission critical because ASA(ALT) PMs operate in a slightly different manner than a traditional warehouse, this process with allow them to successfully mange their inventories.</p> <p><strong>Benefits</strong> <br /> ASA(ALT) PMs will be able to utilize and execute DPAS in accordance with their mission objectives.</p> <p><strong>Users</strong> <br /> This would affect all the ASA ALT community -- users in DPAS (WM).</p> <p><strong>Completed – Release 2020.2.2 – 31 July 2020</strong></p>
20467Deactivate Member Profiles01603WarehouseSPECWARCOMNewSubmitted: 14 May 2020<p><strong>Description </strong> <br /> Member profiles of individuals who are no longer within the Logistics Program are cluttering up all functions that require retrieving an individuals name. Some warehouses try managing their customer base via the customers assigned to their UIC but are unable to do so as it is convoluted with customers who left years ago.</p> <p><strong>Recommended </strong> <br /> Give the ability to deactivate a member profile via a checkbox within their profile. Nothing associated with the member profile would be deleted, but on the front end this particular customer would not appear in any inquiries unless their profile is reactivated.</p> <p><strong>Mission Critical </strong> <br /> Mandated - Although this doesn't stop our users from completing their day to day job it does add time to day to day functions in DPAS and increased user frustration as it leads to inaccurate transactions.</p> <p><strong>Benefits </strong> <br /> This will allow for a cleaner and updated list of individuals within the Logistics Program by reducing the time to querying an individual since it would only need to retrieve active member profiles vice all historical profiles.</p> <p><strong>Users </strong> <br /> All users</p>
20466Adding the Meter Reading to the DW0101604WarehouseAF: AFERMSDoneSubmitted: 13 May 2020<p><strong>Description</strong> <br /> When printing saving the DW01 currently there is no meter reading on the DW01, so we can't see if the computers are down what the meter reading was on the SKO.</p> <p><strong>Recommended</strong> <br /> Add meter reading to DW01 so the equipment can be tracked.</p> <p><strong>Mission Critical</strong> <br /> important</p> <p><strong>Benefits</strong> <br /> time savings</p> <p><strong>Users</strong><br /> all agencies using the meter reading</p> <p><strong>Completed – Release 2020.1.4 – 29 May 2020</strong></p>
20465Creation of New PA Role01602PAAF: GEITNewSubmitted: 5/13/2020<p><strong>Description</strong> <br /> Current PA role in DPAS allows PAs to transfer an asset without the gaining PA seeing a pending transaction.  This allows assets to be transferred without approval of gaining PA. Based on suggestion from DPAS Support team, request a new PA role be created that has all of the current PA capabilities with the addition of forcing designate on transactions.</p> <p><strong>Recommended</strong> <br /> Go forward with DPAS Support team suggestion of creating a new PA role that has all the current PA role capabilities along with the addition of forcing designate on transactions.</p> <p><strong>Mission Critical</strong> <br /> Yes, currently assets are being transferred from on AUIC, UIC, Custodian to another without the approval of the gaining custodian.  This allows assets to be moved within the system without visibility/notification for gaining PAs.</p> <p><strong>Benefits</strong> <br /> Addition of this role/capability would eliminate transactions being processed without gaining PA oversight and provide better overall tracking of equipment transactions.</p> <p><strong>Users</strong> <br /> Yes, this will affect all PAs, which is all users within FF-GEIT.</p>
20464Reports/Forms Search Criteria Addition01601PAAF: GEITNewSubmitted: 5/13/2020<p><strong>Description</strong> <br /> The options for search criteria under View Forms/Reports currently has three drop-down choices even when all 3 are deployed the results generated for a single day are too many to find a report that is more than a day old.  Propose adding additional search criteria to drop-down.</p> <p><strong>Recommended</strong> <br /> Add 3 more search criteria AUIC, Date Range and Rpt Owner.</p> <p><strong>Mission Critical</strong> <br /> Yes, PAs need the ability to easily find reports that were generated more than 24 hours ago.</p> <p><strong>Benefits</strong> <br /> This would greatly reduce the time it takes to find a report and it will reduce the need for duplicate report generation, i.e. Inventories.  The system is storing the data but it’s of no use to those that need it because there are too many pages of reports to find the report that’s needed.</p> <p><strong>Users</strong> <br /> Yes, this will affect all PAs, which is all users within FF-GEIT.</p>
20463Report Build01600WarehouseNavy: NAVSUPNewSubmitted: 5/5/2020<p><strong>Description</strong> <br /> Currently not able to run/manipulate a report that will capture all the data that is required to submit to our higher echelon.  We have a required submission and request to have a report built to meet out needs/requirement.</p> <p><strong>Recommended</strong> <br /> Build a report that will meet our submission requirement.</p> <p><strong>Mission Critical</strong> <br /> Yes, we are required to submit a report to a higher echelon in order to submit qty, line items and financial expenditures.</p> <p><strong>Benefits</strong> <br /> Reduces Time/Cost, Improves/Accuracy/ Accountability, Financial Reporting, Etc.</p> <p><strong>Users</strong> <br /> All users</p>
20462Appointment Inquiry01599WarehouseUSMC: CSPNewSubmitted: 29 Apr 2020<p><strong>Description</strong> <br /> Currently when a clerk begins an Issue or return transaction and backs out of that  transaction without canceling the Issue or Return transaction this transaction will sit in the Appointment Inquiry as In Process which is making it difficult to get a good accurate service time report.</p> <p><strong>Recommended</strong> <br /> Recommend that when an Issue or Return transaction has been sitting in process for 24 Hrs it is automatically canceled.</p> <p><strong>Mission Critical</strong> <br /> Yes, having this functionality will help with the viewing of what is truly in process and what has been completed.  This will also help with proper metrics that are needed on a monthly basis.</p> <p><strong>Benefits</strong> <br /> Having this functionality will help with the accuracy reporting of service time metrics.</p> <p><strong>Users</strong> <br /> Yes All.</p>
20461Army Condition Codes01598WarehouseArmy: ASA(ALT)DoneSubmitted: 04/03/2020<p><strong>Description</strong><br /> When in the Warehouse module,the user is unable to choose the appropriate Army condition code (Army Policy AR 725-50) to show the inventory control record the physical state of the materiel.</p> <p><strong>Recommended</strong><br /> Include the additional Army condition codes (see encl) in the drop down menu.</p> <p><strong>Mission Critical</strong><br /> This is mission critical, Army customers process hundreds of transactions daily in DPAS, without this process it hinders the ability for the customer to properly show the condiction of the materiel they are actioning; current state they are misapplying condition codes based on lack of Army condition codes.</p> <p><strong>Benefits</strong><br /> Adding the Army condition codes will allow us to appropriately validate the materiel while improving accuracy, and accountability aligned to audit. This would also improve internal controls and stream line items affecting Army logistics business processes.</p> <p><strong>Users</strong><br /> This would affect all the ASA ALT community -- users in DPAS (WM).</p> <p><strong>Completed – Script – 14 April 2020</strong></p>
20460Transition Ad Hoc Move from HHT to Web Page01597EnterpriseLeidosDoneSubmitted: 3/24/20<p><strong>Description</strong><br /> DPAS's Handheld Terminal (HHT) executive software is no longer supported by the vendor, thus the devices can no longer be connected to the DoD network. This does not alleviate the functions of the DPAS programs, but rather results in performing these functions manually rather than using AIT automation. This SCR is proposing to transition the Ad Hoc move functionality that resides within the DPAS application to a web application enabling the user to use any approved device that is capable of hosting a DPAS session.</p> <p><strong>Recommended</strong><br /> Develop a web page(s) that provides the capability to move an asset from one location to another or from a location into a container, or from a container to a location by scanning of asset/materiel, location and container labels. Consideration should also be given to supporting pRFID as a read methodology, and supporting planned picks.</p> <p><strong>Mission Critical</strong><br /> Yes, without this capability, there is an increased manpower requirement that cannot be fulfilled.</p> <p><strong>Benefits</strong><br /> Reduced manpower through automated scans, and improves accuracy.</p> <p><strong>Users</strong><br /> All users who move inventory.</p> <p><strong>Completed – Release 2020.3 – 9 October 2020</strong></p>
20459Utilize Agency-Defined Field - Local Equipment ID01596MUAF: SEMISRemovedSubmitted: 3/19/2020<p><strong>Description</strong> <br />AF Support Equipment is physically identified by 5-character equipment IDs that are usually based on the serial number (but not always), and are stenciled, painted, etched, or otherwise attached to make the equipment readily identifiable from 10-15 feet away. In legacy systems, this equipment ID was also used as the asset ID or serial number. DPAS uses a system-generated asset ID and the actual serial number is recorded in the system. The actual serial number is typically too long to reasonably attach to the equipment, and remarking all equipment to accommodate the transition to DPAS is cost and manpower prohibitive. Propose using an agency definable field to allow recording of a locally determined equipment ID.</p> <p><strong>Recommended</strong> <br />Utilized Agency Definable field to create capability to enter and record a locally determined equipment ID. Equipment ID is non-unique and can be changed. Require ability to search by equipment ID and require equipment ID to be reflected on work orders.</p> <p><strong>Mission Critical</strong> <br />This is mission critical. Lack of ability to easily identify equipment will degrade mission effectiveness and increase the risk of damage to combat aircraft. Remarking all SE to reflect actual item serial numbers is cost and manpower prohibitive, and is not possible in many cases due to length of serial number and available space for marking.</p> <p><strong>Benefits</strong> <br />Improves accountability, reduces manpower cost in marking equipment and identifying equipment for dispatch, inventory, or other purpose. Reduces risk to aircraft, munitions, and personnel through ready identification of correct, serviceable SE.</p> <p><strong>Users</strong> <br />This affects all M&U module users within the United States Air Force.</p> <p><strong>25 Sept 2020 – cancelled per Luther J. Meitzner </strong> <br /> Utilizing the DoD Serial Number to fill that purpose.</p>
20458Asset Location and Sub-location Updates01595PAAF: GEITNewSubmitted: 3/10/2020<p><strong>Description</strong><br /> Property Administrators cannot change multiple asset location or sub-location within one transaction. This is not a master data issue. Locations are accurately listed in master data. If an asset is moved physically, the location and/or sub-location needs to be updated from where it is currently listed in DPAS. If there are multiple assets that need to be updated under a UIC, it requires multiple transactions instead of being able to update each asset within one transaction and under one DOC number. Create the capability for PAs to update a complete UIC's assets location and/or sub-location under one transaction.</p> <p><strong>Recommended</strong><br /> Create the capability for PAs to update a complete UIC's assets location and/or sub-location under one transaction. Maybe this can be done by simply adding a save option within the UPDATE under Asset Management. Once all asset updates are completed for that UIC, you click submit and it is all done under one transaction and DOC number. This feature is already in use and available when new assets are added.</p> <p><strong>Mission Critical</strong><br /> This is not mission critical at this time. However, it is extremely time consuming and inconvenient for the PA to make updates using separate transactions and under different DOC numbers.</p> <p><strong>Benefits</strong><br /> This solution will save huge amounts of time for PAs. Assets listed under all UICs within their assigned AUIC, must show accurate location and sub-location in order for their physical locations to be known. Accurate location and sub-location will increase accurate asset accountability and decrease asset loss.</p> <p><strong>Users</strong><br /> This will affect all PAs assigned to FF-GEIT.</p>
20457Location Additions01594PAAF: GEITNewSubmitted:3/10/2020<p><strong>Description</strong><br /> Currently DPAS does not allow user to add new location data on the asset update screen. Only preloaded locations within Master Data may be selected from. Propose allowing user to add locations from the asset update screen rather than having to add to master data every time a new location is needed.</p> <p><strong>Recommended</strong><br /> Add the capability to add location data on the asset update screen instead of updating through the master data function.</p> <p><strong>Mission Critical</strong><br /> This is not mission critical at this time. However, it is very time consuming and inconvenient for the PA to add location data on the master data screen and then go back to the asset update screen to select the location that was added.</p> <p><strong>Benefits</strong><br /> This solution will save time and prevent an unneeded step for PAs. This solution will allow locations to be added on the same screen where they need to be selected rather than adding in master data and then going back to the asset update screen to select.</p> <p><strong>Users</strong><br /> This will affect all PAs assigned to FF-GEIT.</p>
20456Member Site Feedback Area01593WarehouseAF: AFERMSDoneSubmitted: 07 Feb 2020<p><strong>Description </strong> <br /> Need the ability in member site to allow members to select an equipment item off a list and type a narrative for feedback on that equipment item.  Within warehouse, need the ability to pull an inquiry of provided feedback.</p> <p><strong>Recommended </strong> <br /> Add an area within the member site for feedback.  Within feedback area have a dropdown for equipment to select from and then a narrative block for members to type into.  Add an inquiry within warehouse to pull feedback given.  Inquiry needs to have roll-up feature.</p> <p><strong>Mission Critical </strong> <br /> highly desired</p> <p><strong>Benefits </strong> <br /> time savings, data accuracy and staying within one system.</p> <p><strong>Users </strong> <br /> All</p> <p><strong>Completed – Release 2020.1.3 – 8 May 2020</strong></p>
20455Repair parts inquiry by component stock number01592WarehouseAF: AFERMSDoneSubmitted: 07 Feb 2020<p><strong>Description </strong> <br /> Need the ability to have an inquiry that will pull all repair data by component stock number and have a roll-up feature. In theory, if 20 of one component are repaired in different kits it would show one grid line for each component stock number (not kit ICN) and have a qty of 20.</p> <p><strong>Recommended </strong> <br /> Add an area under Inquiries to include this data with a roll-up option.</p> <p><strong>Mission Critical </strong> <br /> highly desired</p> <p><strong>Benefits </strong> <br /> time savings, data accuracy and staying within one system.</p> <p><strong>Users </strong> <br /> All</p> <p><strong>Completed – Release 2020.2 – 26 June 2020</strong></p>
20454DPAS Roles Addition01591WarehouseArmy: ASA(ALT)DoneSubmitted: 02/06/2020<p><strong>Description </strong> <br /> ASA(ALT) community would like to customize roles for its users in support of the mission objectives of the Program Managers.</p> <p><strong>Recommended </strong> <br /> Modify the DPAS roles to custom ALT roles in support of Army business process; create the ALT roles on the attached spreadsheet aligned to business functions required.</p> <p><strong>Mission Critical </strong> <br /> This is mission critical because ASA(ALT) PMs operate in a slightly different manner than a traditional warehouse.  We also need to have super users available to support each organization.</p> <p><strong>Benefits </strong> <br /> ASA(ALT) PMs will be able to utilize and execute DPAS in accordance with their mission objectives.</p> <p><strong>Users </strong> <br /> Yes</p> <p><strong>Completed – Release 2020.1.2 – 17 April 2020</strong></p>
20453Physical Inventory List01590WarehouseNavy: NAVAIRNewSubmitted: 5 Feb 2020<p><strong>Description </strong> <br /> Each Program Office/Commodity Type has a responsibility to maintain a complete inventory of all government owned ST/STE property. Periodically, complete Physical Inventories are conducted at each storage location. This inventory is managed in excel documents, identifying the tool id, condition, and physical storage location. The Program Office manages tens of thousands of production ST/STE for each weapon system, it would be physically impossible and costly to manually update the DPAS database with the current condition and physical storage location for each item after a physical inventory. An automated solution is needed to mass update lists of ST/STE in a timely, cost effective manner.</p> <p><strong>Recommended </strong> <br /> Need to create an import program to upload the Physical Inventories and update the condition and physical location of each tool.</p> <p><strong>Mission Critical </strong> <br /> Mission Critical. In order to be FIAR audit compliant, the program office must be able to reconcile their inventories within DPAS.</p> <p><strong>Benefits </strong> <br /> This correction will reduce Time/Cost for updating physical inventory lists and ensures/improves Accuracy and Accountability of DoD owned ST/STE. It is mandated that the complete list of all DoD owned ST/STE property be managed in DPAS. Currently, it is cost prohibitive to manually update the location and condition of all tooling located at a storage facility after a physical inventory. </p> <p><strong>Users </strong> <br /> All users, it is vital to know where tooling is stored to support the maintainability of the weapon system.</p>
20452New Tool Load to Catalog01589WarehouseNavy: NAVAIRNewSubmitted: 5 Feb 2020<p><strong>Description</strong> <br /> Each Program Office/Commodity Type has a responsibility to maintain a complete inventory of all government owned ST/STE property. Through the eTIMS system, the Program Office receives a listing of any new ST/STE that has been created to support the weapon system. This information needs to be inserted into the DPAS database, so the Program Office has a complete inventory of all government owned ST/STE.</p> <p><strong>Recommended</strong> <br /> Create an import to add new ST/STE into DPAS.</p> <p><strong>Mission Critical</strong> <br /> Mission Critical. In order to be FIAR audit compliant, the program office must be able to reconcile/manage their inventories within DPAS.</p> <p><strong>Benefits</strong> <br /> This correction will reduce Time/Cost for adding new ST/STE and ensures Accuracy and Accountability of DoD owned ST/STE. It is mandated that the complete list of all DoD owned ST/STE property be managed in DPAS. Currently, it is cost prohibitive to manually add large numbers of new ST/STE through the on-line DPAS system.</p> <p><strong>Users</strong> <br /> All users, it is vital to know all ST/STE owned by the DoD to support the weapon system. The users need to know what ST/STE is available to maintain the weapon system.</p>
20451Container as Individual Issue Location01588WarehouseDIANewSubmitted: 1/30/2020<p><strong>Description</strong> <br /> Warehouse Individual Issue provides an auto-pick capability when a Stock Item Individual Issue Location is set for a stock item. It doesn't allow use of a Container as the Individual Issue Location.</p> <p><strong>Recommended</strong> <br /> Allow setting a Stock Item Individual Issue Location at the Container level so an issue transaction can auto-pick required quantities.</p> <p><strong>Mission Critical</strong> <br /> This is a time and resource saving change.</p> <p><strong>Benefits</strong> <br /> Reduce time (clicks) to process an Issue transaction.</p> <p><strong>Users</strong> <br /> Warehouse users performing Issue transactions.</p>
20450USMC NAF CIP Enhancements01587PALeidosNewSubmitted: 29 Jan 2020<p><strong>Description</strong> <br /> Enhance existing DPAS CIP to support USMC NAF requirements.</p> <p><strong>Recommended</strong> <br /> Develop the functionality to support tracking CIP costs by Development Phase. Add logic to display fields based on Project Phase and Project Type. Add approximately 10 new fields (operational category, POET, Funding Purpose, etc). Develop functionality to calculate ROI based on customer's calculation.  Add functionality to track CIP Funding by RPUID. Develop ability to track CIP Projects over 5 phases (Bid, Design, Construction, etc). Add logic to display fields based on Project Phase and Project Type. Adjust current CIP Real Property to allow users to create CIP shell with fewer required fields.  Create a Facility Condition Report.</p> <p><strong>Mission Critical</strong> <br /> Currently DPAS does not support this functionality.  This would be necessary to support USMC NAF's requirements.</p> <p><strong>Benefits</strong> <br /> Improvements to Accuracy, Accountability, Financial Reporting.</p> <p><strong>Users</strong> <br /> This would provide additional functionality to all DPAS Real Property users.</p>
20449USMC NAF Work Order Tool01586PALeidosNewSubmitted: 29 Jan 2020<p><strong>Description</strong> <br /> Build a Work Order tool to support USMC NAF maintenance and repairs.</p> <p><strong>Recommended</strong> <br /> Develop a tool to log, track, and support building maintenance and support and associated tasks and work orders. The tool will include the ability to schedule preventative maintenance on a recurring basis (e.g. Annual Check/Maintenance of the HVAC system).  tab within the RP asset that allows the user to view all of the Work Orders associated to that RP asset. Provide sufficient summary information to know what the WO was for with a hyper link to display the specific Work Order in a new Browser window. Store record of work orders performed on asset, populated from work order tool and ability to enter records.</p> <p><strong>Mission Critical</strong> <br /> Currently DPAS does not support this functionality.  This would be necessary to support USMC NAF's requirements.</p> <p><strong>Benefits</strong> <br /> Improvements to Accuracy, Accountability, Financial Reporting.</p> <p><strong>Users</strong> <br /> This would provide additional functionality to all DPAS Real Property users.</p>
20448USMC NAF Real Property Enhancements01585PALeidosDoneSubmitted: 29 Jan 2020<p><strong>Description</strong> <br /> The current Real Property functionality in DPAS needs enhanced to support USMC NAF Real Property needs.</p> <p><strong>Recommended</strong> <br /> Develop a means to realize RP CIP to the property book, develop ability to setup and manage a RP Improvement. Build a new tab to track Facility maintenance. Build a new tab to track CIP Improvements and projects associated with the Real Property asset. Build functionality to track funding for the Real Property asset. Develop tests to track facility maintenance spend and facility condition.</p> <p><strong>Mission Critical</strong> <br /> Currently DPAS does not support this functionality. This would be necessary to support USMC NAF's requirements.</p> <p><strong>Benefits</strong> <br /> Improvements to Accuracy, Accountability, Financial Reporting.</p> <p><strong>Users</strong> <br />T his would provide additional functionality to all DPAS Real Property users.</p> <p>Linked to <a href="index.php/support/system-change-request/details/4/20483/real-property?start=0">SCR #01620</a></p> <p><strong>Completed – Release 2020.3.2 – 13 November 2020</strong></p>
20447USMC NAF Project Planning Tool01584PALeidosIn ProgressSubmitted: 29 Jan 2020<p><strong>Description</strong> <br /> Build a Project Planning tool within CIP to support USMC NAF Real Property life cycle management.</p> <p><strong>Recommended</strong> <br /> Build a minimum viable product project planning tool.  The tool will include:  Additional fields to support different phases; ability to track through submitted / approved / design / construction; ability to pull in projects from Microsoft project; ability to build projects with associated funding fields, category types, calendars with alerts; Single Use Projects and Multi Use Projects; Project sub types: Capital Improvement and Maint.</p> <p><strong>Mission Critical</strong> <br /> Currently DPAS does not support this functionality. This would be necessary to support USMC NAF's requirements.</p> <p><strong>Benefits</strong> <br />Improvements to Accuracy, Accountability, Financial Reporting.</p> <p><strong>Users</strong><br />This would provide additional functionality to all DPAS Real Property users.</p> <p><strong>Partially Completed - Release 2021.3 - 10 Sept 2021</strong></p>
20446USMC NAF CIP Funding01583PALeidosNewSubmitted: 29 Jan 2020<p><strong>Description</strong> <br /> Enhance existing DPAS CIP Funding to support USMC NAF requirements.</p> <p><strong>Recommended</strong> <br /> Develop the functionality to support multiple Funding sources to support development phase. Add ability to decrement funding based on funding phases and costs. Build a grid display to show all funding documents and the totals for all funding documents. Automation of USMC funding docs via GEX interface. Fix Source Desc Display.</p> <p><strong>Mission Critical</strong> <br /> Currently DPAS does not support this functionality. This would be necessary to support USMC NAF's requirements.</p> <p><strong>Benefits</strong> <br /> Improvements to Accuracy, Accountability, Financial Reporting.</p> <p><strong>Users</strong> <br /> This would provide additional functionality to all DPAS Real Property users.</p>
20445New Form in Unit Issue Request and Transfer Process01582EnterpriseNavy: NAVAIRNewSubmitted: 23 JAN 2020<p><strong>Description</strong> <br /> The existing ST/STE database, eTIMS, generated a form called a "C-List" for every request created. The "C-List" contained: who created the request, who the list is addressed to (warehouse if a unit issue request, or vendor if an issue transfer), request number, date request created, aircraft, comments (remarks), ST/STE list, contract, UIC, expected return date, ship to (UIC and address), ship to contact (name and phone). The closest thing to this form in DPAS is the Issue Receipt form. This form does not have some information which used to be on the "C-List." Also, the Issue Receipt is only available once a UIR is Issued. NAVSUP WSS requires a form be generated upon the completion of a UIR on their end (once the UIR's status changed to PK-Picking). As of now, they have to take screen shots of the UIR page to provide to PCOs and vendors to show we have completed the request. A sample C-List from eTIMS and an example of what the new form should look like will be provided with the submittal of this SCR.</p> <p><strong>Recommended</strong> <br />Create a new form that includes all information as the provided C-List, or update the Issue Receipt to include this information.  The information that should be included on the form should be: Unit Issue Request Established By, Established Date/Time, To, Request or Transfer #, Reportable Commodity Type, Remarks (mainly for TAC information), Tooling List, UIC, Account Name, Expected Return Date, Ship to Address, and Contact Information of UIC Custodian.  Make this form available to view and print when the request is "In-Process" or "Pk-Picking" status. Also make this form available during the Unit Issue Transfer process.</p> <p><strong>Mission Critical</strong> <br />Mandated. Vendors and PCOs require some type of documentation to use as a receipt that the UIR has been started/completed. DCMA uses this documentation when inspection occurs, PCOs use this document when modifying their contracts.</p> <p><strong>Benefits</strong> <br />This solution will create a formal document that we can use as proof of completing a UIR. It will improve accountability and standardize the UIR process.<br /><br /></p> <p><strong>Users</strong> <br />This change will impact not only users of DPAS and the ST/STE community, but DLA, NAVSUP WSS, and NAVAIR PCOs/ACOs. Vendors also rely on a formal document as an inspection point that a UIR has been completed.</p>
20444Update Expected Return Date01581EnterpriseNavy: NAVAIRNewSubmitted: 23 JAN 20<p><strong>Description</strong> <br /> There are 3 categories of ST/STE requests:</p> <ol> <li>Warehouse Requests (ST/STE is stored at a warehouse and is requested to be shipped to a location for usage)</li> <li>Contract Transfers (ST/STE is staying at the current location, but changing its contract accountability)</li> <li>Loan Extensions (ST/STE is staying at the current location and being used under the current contract, but the expected return date needs changing).</li> </ol> <p>The Unit Issue Request process works well for warehouse requests. However, for Contract Transfer Requests, utilizing the existing Unit Transfer Request process does not give us the ability to update the expected return date. There also isn't a separate process to allow for updating return dates when processing Loan Extension requests.  Lastly, Open Warehouse Actions for Unit Returns are not updating when an expected return date is updated.<br />The work around we have been using in order to add return dates is to return ST/STE to the warehouse, then issue it back out with a Unit Issue Request with a return date. This is creating unnecessary rework and longer touch times and cycle times to complete requests.</p> <p><strong>Recommended</strong> <br /> Incorporate the ability to add an expected return date to the Unit Transfer Request process and the ability to update the expected return date to ST/STE on loan (without transferring the contract). Accommodate the Contract Transfer and Loan Extension Requests described above.  Open Warehouse Actions for Unit Returns need to be updated when expected return dates are updated.</p> <p><strong>Mission Critical</strong> <br /> Mission critical. ST/STE must have accurate expected return dates in order to have proper accountability and traceability.</p> <p><strong>Benefits</strong> <br /> This implementation should reduce the cycle time to complete Unit Transfers and Loan Extensions by at least 67%.</p> <p><strong>Users</strong> <br /> This change will impact not only users of DPAS and the ST/STE community, but it will improve fleet readiness by allowing us to complete requests much faster than we currently do.</p>
20443Physical Inventory Commodity Type discrepancy01580EnterpriseNavy: NAVAIRNewSubmitted: 23 JAN 2020<p><strong>Description</strong> <br /> Each Program Office/Commodity Type has a responsibility to do a wall-to-wall inventories of all government owned property.  When conducting physical inventories within DPAS, often multiple commodity types will show up in one location.  This is a problem because DPAS will not let one commodity type to reconcile their inventory when another commodity type is in the same location. </p> <p><strong>Recommended</strong> <br /> Recommending that when conducting physical inventories, let each commodity type reconcile the ST/STE inventory they own within that location.   </p> <p><strong>Mission Critical</strong> <br /> Mission critical.  In order to be FIAR audit compliant, the program offices must be able to reconcile their inventories within DPAS.</p> <p><strong>Benefits</strong> <br /> This correction would all for all commodities to complete physical inventory reconciliations and be in FIAR audit compliance.</p> <p><strong>Users</strong> <br /> This change will impact not only users of DPAS and the ST/STE community, but it will improve fleet readiness by allowing us to insure that the ST/STE inventory is 100% accurate.</p>
20442Expanding Stock Number Field01579EnterpriseNavy: NAVAIRNewSubmitted: 23 JAN 2020<p><strong>Description</strong> <br /> NAVAIR is responsible for managing Special Tooling/Special Tooling Equipment associated with various weapon systems/reportable commodity types.   Manufacturing numbers that are created by vendors are used for the stock numbers of the tools.  However, the vendors' manufactured numbers have been known to be 25+ long.  The length of these numbers are not standardized across vendors.  More than 15 characters are assigned to ST/STE to uniquely identify the tool.  As such the current solution prevents the use of the Stock Number field and the associated capability within the DPAS system.   The Special Tooling Identifier is part of the Stock Number Description Field along with the Noun.  In addition, this practice makes it difficult to utilize the Master List Capability to building Tool to Tool and Tool to Part relationships. <br /> The conversion into DPAS utilized a unique identifier from the source systems primary key, but after conversion future entries will require the generation of a unique DPAS key.  Loading large numbers of ST/STE from OEM will be further complicated as the OEM assign the Tool ID and the current practice of using the Stock Number Description will not trap duplicate entries on the Catalog.</p> <p><strong>Recommended</strong> <br /> Request the expansion of the current 15 character limit of the Stock Number field to 30 characters in the Warehouse Module to accommodate future Special Tooling and Special Tooling Equipment (ST/STE).</p> <p><strong>Mission Critical</strong> <br /> Mission Critical.  Over time the management of ST/STE by NAVAIR will be hampered with duplicate Catalog entries due to the 15 Character limit in the Stock Number field.  Future assignment of Inventory to the catalog and asset reporting will be hindered.  Duplicate Stock Number entries (via a description) will challenge audit-ability of this data.</p> <p><strong>Benefits</strong> </p> <ol> <li>Tight control of the Tooling Catalog</li> <li>Reduce workload on finding tooling associated with weapon system BOMs</li> <li>Full benefit and reporting capability offered by the Stock Number Field</li> <li>Easier loading of future PPSA files</li> <li>Elimination of duplicate Catalog entries and association of Inventory to Catalog entries, removal of future audit findings.</li> </ol> <p><strong>Users</strong> <br /> This change will impact current Navy ST/STE community and potentially the Air Force ST/STE community.  Additionally any future or current community for which the Stock Number field proves to be too short.</p>
20441Transaction Review Report01578PADIANewSubmitted: 1/22/2020<p><strong>Description</strong> <br /> Require a report of all transactions for a date range.</p> <p><strong>Recommended</strong> <br /> Create new report, like the Increase Decrease Actions report, that captures all changes to asset records, not just Increase/Decrease.</p> <p><strong>Mission Critical</strong> <br /> Mandated by agency Process Cycle Memo (PCM) for auditability.</p> <p><strong>Benefits</strong> <br /> Improves accuracy and enables assertion of completeness.</p> <p><strong>Users</strong> <br /> All DPAS users in our agency.</p>
20440Automate System Access Requests01577EnterpriseAF: GEITNewSubmitted: 1/22/2020<p><strong>Description</strong> <br /> The process for requesting access to DPAS is antiquated/not user friendly and is an analog process.  Propose automating the entire access request process and housing it on the DPAS site.</p> <p><strong>Recommended</strong> <br /> Recommend automating the DPAS access request process by developing a process and housing it on the DPAS site.  Many sites the DoD uses have automated access request systems housed on the site access is being requested to.  Current DPAS access process has users download documents from the DPAS site, fill out the Documents, route for signature, and then have the IO review and upload the documents on the DPAS site.  Recommend a virtual access request system be housed on the DPAS site and automate the routing and review process like many other DoD sites.  The previous system utilized for IT asset Management AFEMS/AIM had this capability if an example is needed.</p> <p><strong>Mission Critical</strong> <br /> Yes, automating this process would save hundreds of man hours spent downloading, reviewing and then uploading documents.  Documents can be created virtually and can disperse data where needed.  The current process is extremely cumbersome and time consuming.  So much to the point where SAF/A4 has stood up a help desk and hired contractors to process access request documents for users.</p> <p><strong>Benefits</strong> <br /> If a user requesting access can do so on the site without downloading documents and routing them, hundreds of man hours can be saved and data integrity will improve by limiting the selections a user can make and routing the request to the appropriate approval authorities.  The automation of this process will save time for the user, IO, DPAS Security Team and any other offices/agencies currently involved in the access request process.</p> <p><strong>Users</strong> <br /> Yes, this will affect all users of DPAS.</p>
20439New Role01576WarehouseNavyNewSubmitted: 01/16/2020<p><strong>Description</strong> <br /> Navy Weapons Division requires a new Role to be created to support the business process we require from the DPAS Warehouse Application</p> <p><strong>Recommended</strong> <br /> Create a new role that limits the access to the application to specifically to processes that are needed to support our business process</p> <p><strong>Mission Critical</strong> <br /> Mission Critical - creating a new role will reduce the training requirement for our users and reduce the unnecessary requirement to ignore unneeded processes</p> <p><strong>Benefits</strong> <br /> Reduces Time and Cost associated with using the DPAS Warehouse application</p> <p><strong>Users</strong> <br /> Only effects our users</p>
20438Inventory Activity added to role01575WarehouseNavy: NAVAIRDoneSubmitted: 15 January 2020<p><strong>Description</strong> <br /> I have a Northrup Grumman contractor, Debbie Kassay who works for PMA 231.  Currently she has DPAS Stakeholder access, and needs Inventory Activity added to her role.  I have been working with DPAS Support to have Inventory Activity added to her and they suggested that I submit an SCR. </p> <p><strong>Recommended</strong> <br /> Have Inventory Activity added to Debbie Kassay Stakeholder role.</p> <p><strong>Mission Critical</strong> <br /> Yes, with all of the mandated SECNAV Inventory requirements currently in place, Debbie Kassay cannot view the inventory activity required to do her job.</p> <p><strong>Benefits</strong> <br /> Benefits of her getting access would improve financial accountability of tooling being issued to vendors out on contract.</p> <p><strong>Users</strong> <br /> It would affect all users who have stakeholder access.</p> <p><strong>Completed – Release 2020.1.1 – 27 March 2020</strong></p>
20437Add ILS-S parts requisition capability to M&U01574MUAF: SPT EQUIPDoneSubmitted: 13 January 2020<p><strong>Description</strong> <br /> Require capability to create a supply requisition in M&U against a given job and serial number, and have requisition pass to ILS-S. <br /> Require capability for ILS-S to process transaction and return appropriate status to M&U for documentation on job order and in history for that end-item.</p> <p><strong>Recommended</strong> <br /> Create linkage/interface with ILS-S to accommodate parts requisitioning against a given job and serial number.</p> <p><strong>Mission Critical</strong> <br /> This is mission critical. <br /> The ability to seamlessly requisition parts is a critical component of maintaining Air Force wartime mission capability. <br /> The lack of an interface requires maintainers/users to manually translate information between systems; increasing time-lines, likelihood of errors and potentially delaying sortie generation and the Air Force's ability to support wartime missions. <br /> Maintaining requisition transactions in asset history provides crucial information to enable financial planning and fleet repair/replacement decision making.</p> <p><strong>Benefits</strong> <br /> Improves status reporting accuracy of support equipment, Air Force readiness reporting, financial plans/budget reporting, and program management offices' fleet sustainment planning.</p> <p><strong>Users</strong> <br /> This affects all M&U module users within the United States Air Force.</p> <p> </p> <p> </p> <p> </p> <p><strong>Partially Completed -- Release 2021.2 - 28 May 2021</strong></p> <p> </p> <p><strong>Completed - Release 2021.3 - 10 September 2021</strong></p>
20436AEMM Bulk MGN01573EnterpriseArmy: ASA(ALT)DoneSubmitted: 1/13/2020<p><strong>Description</strong> <br /> Defense Property Accountability System (DPAS) and Army Serialization Business Rule Constraints. <br /> A system business rule created to support the information exchange between the Army Enterprise Integration Program (AESIP) Army Equipment Materiel Master (AEMM)  and the DPAS Catalog is causing issues with managing items in DPAS for property accountability for serialized items; when data is fed from the AEMM (the Army's master catalog) to DPAS a record with a blank Serial Number Indicator (SNI) (necessary in support of AD 2016-21) the materiel is handled as bulk. <br /> This is effecting users within both the ASA(ALT) and AMC communities. </p> <p><strong>Recommended</strong> <br /> For the Army customer, instead of the materiel being handled as bulk, the serialization field in DPAS (for items without a SNI) will allow PBOs to continue bringing the property to record with an edit capability and provide "recommended" serialization code in their local account catalog, with a report generated by DPAS so that the Army community can expedite the adjudication of these items.</p> <p><strong>Mission Critical</strong> <br /> This is mission critical for audit and transparency. Instead of the materiel being handled as bulk, the serialization field in DPAS (for items without a SNI) will allow PBOs to continue bringing the property to record with an edit capability and provide "recommended" serialization code in their local account catalog.</p> <p><strong>Benefits</strong> <br /> Adding the modification would reduce reprocessing time, improve accuracy, and accountability aligned to audit.  This would stream line items affecting Army logistics business processes.</p> <p><strong>Users</strong> <br /> Yes.</p> <p><strong>Completed – Release 7.2.40 – 31 Jan 2020</strong></p>
20435Disposition Excess01572WarehouseUSMC: CSPNewSubmitted: 9 Jan 2020<p><strong>Description</strong> <br /> Currently the Disposition “Excess” process does not fully support DoD 4140.01 / DLMS processing for excess material being sent to DLA Disposition Services .</p> <p><strong>Recommended</strong> <br /> Recommend the following requirements:</p> <ol> <li>Produce an “Excess” formatted DD Fm 1348-1a and addendums, as necessary</li> <li>Produce a DLMS 856S transaction for the Excess materiel that includes Shipment information (Mode of Shipment, Shipment Date, Shipment Nbr, SCAC, etc.)</li> <li>When the materiel is updated to shipped, the system should be establishing an Intransit within Materiel Mgmt</li> <li>Accept the 527R MRA from DLA to close the Intransit.</li> <li>Work Flow Approval….</li> </ol> <p><strong>Mission Critical</strong> <br /> Yes, having this functionality will make CSP audit compliant in the disposition excess process.</p> <p><strong>Benefits</strong> <br /> Having this functionality will help the CSP be in compliance with the current Marine Corps Audit Readiness Program.</p> <p><strong>Users</strong> <br /> Yes All.</p>
20434Vehicle Type-Group Cd01571MUOSDNewSubmitted: 09 January 2020<p><strong>Description</strong> <br /> With the evolution of DPAS capability, lease cost data will not be determined for GSA SIN as originally established. So during the MAM process, the association between Vehicle Type Cd and Vehicle Group Cd can be reduced to three selections.  Having all the previous selections confuses users trying to match old SINs to new vehicles.</p> <p><strong>Recommended</strong> <br /> Update Vehicle Group Cd table to reflect only GSA Leased, Commercially Leased and Owned for each Vehicle Type Cd.</p> <p><strong>Mission Critical</strong> <br /> Since the Vehicle Type Cd is the only data sent to FAST, I would not say it was mandated unless there are some background issues.  But it does increase time of MAM trying to match Type and Group Cds.</p> <p><strong>Benefits</strong> <br /> Reduces time profiling and improves the accuracy of data.</p> <p><strong>Users</strong> <br /> Only Fleet Operations.</p>
20433Back-Order Report01570WarehouseAF: USAFANewSubmitted: 08 Jan 2020<p><strong>Description</strong> <br /> No report is available to provide data for items currently back-ordered.  Routine replacement orders may contain items back-ordered for specific customers.  There is currently no way to determine which items need to be earmarked for those members.</p> <p><strong>Recommended</strong> <br /> Develop report that shows by all back-ordered items by member.</p> <p><strong>Mission Critical</strong> <br /> Mission critical - items back-ordered for cadets cannot be issued to them upon receipt.</p> <p><strong>Benefits</strong> <br /> Ability to support USAFA mission by ensuring back-ordered items are delivered to those waiting members.</p> <p><strong>Users</strong> <br /> All</p>
20432Consumption Report01569WarehouseAF: USAFADoneSubmitted: 08 Jan 2020<p><strong>Description</strong> <br /> No report is available to provide consumption data for items.  USAFA uses this data to re-order mandatory cadet items.  How many of each stock number (size of uniform item) sold within a period of time is necessary to ensure correct re-order.</p> <p><strong>Recommended</strong> <br /> Develop report that shows by LIN/TAMCN / ITEM the quantities of items sold to cadets for a designated period of time.</p> <p><strong>Mission Critical</strong> <br /> Mission critical - reorder cannot be successful without this information, cadets may not have mandatory uniform/training items available to complete their missions.</p> <p><strong>Benefits</strong> <br /> Ability to re-order mandatory items accurately.</p> <p><strong>Users</strong> <br /> All</p> <p><strong>Completed – Release 2020.2 – 26 June 2020</strong></p>
20431Environmental and Disposal Liabilities Business Process Requirements01568PADISANewSubmitted: 1/3/2020<p><strong>Description</strong> <br /> Calculation of Environmental and Disposal Liabilities (E&DL)</p> <p><strong>Recommended</strong> <br /> See attached document</p> <p><strong>Mission Critical</strong> <br /> E&DL reporting is mandated by SFFAS 6, TR-11, & FMR Vol 4, Chapter 13.</p> <p><strong>Benefits</strong> <br /> DPAS will be the first APSR to implement E&DL for financial reporting purposes. This will save the department time, cost and effort in financial reporting of E&DL of assets within the financial statements.</p> <p><strong>Users</strong> <br /> All Agencies are required to calculate and report E&DL</p>
20430DLMS Columns Added01567EnterpriseUSMC: CSPDoneSubmitted: 20 Dec 2019<p><strong>Description</strong> <br /> During the past Audit Readiness Inspection for the CSP it was noted that extra Columns are needed to be added to the Inquiry>DLMS Transaction Inquiry Review area to make the CSP compliant with the current Marine Corps Audit Readiness policies and to help improve with the quarterly financial reporting requirements.</p> <p><strong>Recommended</strong> <br /> To help with the CSP to be compliant with the current Marine Corps Audit Readiness program we are requesting that the Below columns be added to the following area Inquiry > DLMS Transaction Review: <br />Warehouse > Warehouse_from > To_Owning_DODAAC > From_Owning_DODAAC > From_Location_ID > To_Location_ID > Lst_Updtd_By > As_of_Dt_Tm > Document_Nbr > DIC > Serial_Nbr > Stock_Number > NIIN > Nomenclature > SAC > Type_Asset_Cd > To_Reason_Cd > Description > From_Qty > To_Qty > TOT_QTY > From_Condition_Cd > To_Condition_Cd > Unit_Price > Extended Price > Transaction_Type > Inv_Adj > <br /> GL Account > Change_from_reason_desc > Recoverablity_code > TAMCN</p> <p><strong>Mission Critical</strong> <br /> Yes, without these columns the CSP is forced to rely on multiple data pulls for financial reporting and we are not in compliance with the current Marine Corps Audit Readiness Program.</p> <p><strong>Benefits</strong> <br /> Having this functionality will help the CSP be in compliance with the current Marine Corps Audit Readiness Program.</p> <p><strong>Users</strong> <br /> Yes All.</p> <p><strong>Completed – Release 2021.1 – 5 February 2021</strong></p>
20429Data on DD1348-1A01566WarehouseArmy: ASA(ALT)DoneSubmitted: 19 Dec 19<p><strong>Description</strong> <br /> When processing (print) a DD 1348-1A during the materiel release order (MRO) the continuation form will only print six serial numbers with UII data.</p> <p><strong>Recommended</strong> <br /> Allow the DD 1348-1A continuation sheet to print up to 25-50 serial numbers with UII information.</p> <p><strong>Mission Critical</strong> <br /> This is mission critical, Army customers process hundreds of transactions daily in DPAS, the quantities they field per unit could range from one through the hundreds, without this process the user receives numerous paperwork which they need to review and sign.</p> <p><strong>Benefits</strong> <br /> Adding the modification would reduce reprocessing time, improve accuracy, and accountability aligned to audit.  This would stream line items affecting Army logistics business processes.</p> <p><strong>Users</strong> <br /> This would affect all the ASA ALT community -- users in DPAS (WM).</p> <p><strong>Completed – Release 2020.2 – 26 June 2020</strong></p>
20428Inventory By Exception Button01565PADISANewSubmitted: 18 Dec 2019<p><strong>Description</strong> <br /> DISA would like to include a selection button within the PA Module to identify assets  approved to be inventoried by exception (Maintenance, Third Party, Network Detection, .  (See attached DISA Draft Inv By Exception Process Flow & Checklist Determination)</p> <p><strong>Recommended</strong> <br /> Option #1:Populate an Inventory By Exception selection criteria within "Inv Mgt Plan" data.   <br />Option #2: Populate an Inventory By Exception selection within Asset Management/Update/Basic by adding Inv By Exception data field.</p> <p><strong>Mission Critical</strong> <br /> The Inventory By Exception field provides DISA with an alternate tracking mechanism to assist with inventory of off-site or property housed in another Agencies facility with strict access or budget constraints to satisfy DoD annual inventory requirement IAW 5000.64.  This will be helpful during audit validating asset location verse human touch.</p> <p><strong>Benefits</strong> <br /> DISA Workforce Service Directorate (WSD) is responsible for managing all DISA asset inventories  and this will reduce man-hours, time, cost, and improve accuracy of inventory within a timely manner to meet DoD 98% annual inventory requirement.  </p> <p><strong>Users</strong> <br /> Yes, this action affects all users outlined above within the Agency.</p>
20427Warehouse Receiving Improvements01564WarehouseLeidosDoneSubmitted: 2019-12-16<p><strong>Description</strong> <br /> Users need a way to efficiently and quickly work with upwards of 4000 serial numbers in one receipt.</p> <p><strong>Recommended</strong> <br /> This should be resolved in 2 phases.  The first phase is to allow batch upload of verified and accepted items in receiving via a spreadsheet.  The spreadsheet should be dynamically generated based on the stock number being received to minimize the possibility of user error.  The second phase would be to update the existing screens to allow users to just enter a list of serial numbers, while entering in any needed manufacturer or inspection information only once for that list of serial numbers.  Allow users to repeat that process as much as needed for different manufacturer/inspection information.</p> <p><strong>Mission Critical</strong> <br /> Mission critical, because as it stands now, users cannot reliably or efficiently receipt for more than a hundred or so serialized items at one time.  New groups coming onto DPAS need to receipt for thousands of items at one time.</p> <p><strong>Benefits</strong> <br /> The main benefit of this is reduced time and cost, and improved accuracy.</p> <p><strong>Users</strong> <br /> All users</p> <p><strong>Completed – Release 2020.1.1 – 27 March 2020</strong></p>
20426Cancel Customer Requisition01563Materiel ManagementArmy: ASA(ALT)DoneSubmitted: 16 Dec 2019<p><strong>Description</strong> <br /> When in the ICP module, the user is unable to cancel a customer requisition, they only have the option to refer or send status.  To cancel a customer requisition the user must generate a HDT to process the cancellation.</p> <p><strong>Recommended</strong> <br /> Add the cancel option to the drop down menu under the ICP Module; customer requisition review action tab. This would allow the user the option to select cancel requisition once they find a discrepancies requiring the action be canceled. </p> <p><strong>Mission Critical</strong> <br /> This is mission critical, Army customers process hundreds of transactions daily in DPAS, without this process the customer must rely on the HDT process to clean up actions with their system. </p> <p><strong>Benefits</strong> <br /> Adding the modification would reduce reprocessing time, improve accuracy, and accountability aligned to audit.  This would stream line items affecting Army logistics business processes.</p> <p><strong>Users</strong> <br /> This would affect all the ASA ALT community -- users in DPAS (WM).</p> <p>Part of <a href="index.php/support/system-change-request/details/4/20003/modify-dpas-to-support-the-receipt-and-mgmt-of-customer-requisitions?start=0">SCR 01177</a>.</p> <p><strong>Completed – Previous Release – 31 Aug 2020 – per Kristian Stennett's email</strong></p>
20425Cost Center Drop Down in MRO01562Materiel ManagementArmy: ASA(ALT)NewSubmitted: 16 Dec 2019<p><strong>Description</strong> <br /> When in the ICP module, the user is unable to choose from multiple cost centers (out of the fielding warehouse) to action various inventory.</p> <p><strong>Recommended</strong> <br /> Have a drop down menu inside the ICP module of all cost centers to allow the user to pick from the cost center at time of MRO build - to select which Cost Center should be fielding it - or leave it blank.</p> <p><strong>Mission Critical</strong> <br /> This is mission critical, Army customers processed hundreds of transactions daily in DPAS, without this process it allows the user to generates multiple MRO in a timely manner. </p> <p><strong>Benefits</strong> <br /> Adding the modification would reduce reprocessing time, improve accuracy, and accountability aligned to audit.  This would stream line items affecting Army logistics business processes.</p> <p><strong>Users</strong> <br /> This would affect all the ASA ALT community -- users in DPAS (WM).</p>
20424Field Lock for MROs01561Materiel ManagementArmy: ASA(ALT)NewSubmitted: 16 Dec 2019<p><strong>Description</strong> <br /> When in the ICP module, under material management, creating a requisition, when saving the process, there is no fail safe to allow the user to complete the task with out manually exiting the process. The user is unaware after hitting save one the must exit out, if they continue to hit save it creates multiple MRO with suffixes that can only be reversed by submitting a HDT to DPAS.</p> <p><strong>Recommended</strong> <br /> Have a internal control built into the system so once the MRO save button is hit by the user it locks the process down and move them into another menu to continue on with their additional functions. Or have a pop up to alert the user the document is being processed and not to hit the save button again as it will generate another MRO with a suffix.</p> <p><strong>Mission Critical</strong> <br /> This is mission critical, Army customers processed hundreds of transactions daily in DPAS, without this process it allows the user to generates multiple MRO which cannot be adjusted without submitting a HDT to remove.</p> <p><strong>Benefits</strong> <br /> Adding the modification would reduce reprocessing time, improve accuracy, and accountability aligned to audit.  This would also reduce the backlog and stream line items affecting Army logistics business processes.</p> <p><strong>Users</strong> <br /> This would affect all the ASA ALT community -- users in DPAS (WM).</p>
20423Mandatory Fields in Customer Profile01560Materiel ManagementArmy: ASA(ALT)DoneSubmitted: 16 Dec 19<p><strong>Description</strong> <br /> The requirement to add select items as mandatory when establishing the customer profile, is creating friction points for the Army customer. The mandatory fields for FAD, media status and conditional codes are should be applied when the customer requisition is built not at time of customer profile creation, theses codes fluctuate based on requirements at time of creation and are not universal like the other mandatory fields. </p> <p><strong>Recommended</strong> <br /> Do not make the FAD, media status, and condition code mandatory fields in the customer profile build, allow them to be static.  Make these codes mandatory in the customer requisition (already available and it pulls forward what was in the Customer Profile - can override them; however, there shouldn't be a default).</p> <p><strong>Mission Critical</strong> <br /> This is mission critical, Army customers will process hundreds of customer requisitions daily in DPAS, without this process it hinders the ability for the customer in make adjustments in DPAS to execute and is causing delays with the fielding missions.  ASA(ALT) will prebuild all Army customers with static data - but the media code, condition code, etc. varies by fielding type - however, all PEOs conduct fielding's to the same units - so these codes need to be fluid by requisition.</p> <p><strong>Benefits</strong> <br /> Adding the modification would reduce reprocessing time, improve accuracy, and accountability aligned to audit.  This would also reduce the backlog and stream line items affecting Army logistics business processes.</p> <p><strong>Users</strong> <br /> This would affect all the ASA ALT community -- users in DPAS (WM).</p> <p><strong>Completed – Release 2020.2 – 26 June 2020</strong></p>
20422Bulk Assembly of SKOs01559WarehouseArmy: ASA(ALT)RemovedSubmitted: 16 Dec 19<p><strong>Description</strong> <br /> As a result of us trying to bulk assemble multiple kits that have serialized items.  There isn't a mechanism to plan an assembly for multiple kits that contain serialized components.</p> <p><strong>Recommended</strong> <br /> When ordering the assembly of hundreds of kits that contain serial items, the assembly process should flag that there are serialized components and they have to individually assemble, you should be able to place one order for all their kits.  So instead of doing 800 individual orders for any one item, you could than do sets of 20/30/40 based on fielding schedule and have the locations do the assemblies the way they are.</p> <p><strong>Mission Critical</strong> <br /> This is mission critical, Army customers processed hundreds of transactions daily in DPAS, without this process it hinders the ability for the customer in make adjustments in DPAS to execute the serialization and IUID process and is causing delays with the fielding missions.</p> <p><strong>Benefits</strong> <br /> Adding the modification process to the assembly process would reduce reprocessing time, improve accuracy, and accountability aligned to audit.  This would also reduce the backlog and stream line items affecting Army logistics business processes.</p> <p><strong>Users</strong> <br /> This would affect all the ASA ALT community -- users in DPAS (WM).</p> <p><strong>09 Jan 2020 – cancelled per Lisa Kelly </strong> <br /> DPAS currently possesses the functionality ASA(ALT) needs.</p>
20421WAWF GFP TS Improvements01558PALeidosDoneSubmitted: 12/12/2019<p><strong>Description</strong> <br /> Currently DPAS WAWF GFP TS transactions do not include improvements made in ECP1138.  Additionally, there is some need to adjust previous efforts to allow GFP to transmit GFP TS transactions without UII.</p> <p><strong>Recommended</strong> <br /> Implement changes made in ECP1138 allowing DPAS to transmit WAWF GFP TS transactions with Cage/Part Number, Model Number.  This will include changes to the XML generated by WPHRI02, the likely addition of Model Nbr to WPHRN51, modifications to WCGLX40 to accept new identifiers, and additional validations within WCGLX41. </p> <p><strong>Mission Critical</strong> <br /> Currently DPAS cannot successfully transmit most WAWF GFP TS transactions to PIEE</p> <p><strong>Benefits</strong> <br /> Improvements to Accuracy, Accountability, Financial Reporting</p> <p><strong>Users</strong> <br /> This is impacting all DPAS users trying to transmit WAWF GFP TS transactions</p> <p><strong>Completed – Release 2020.2 – 26 June 2020</strong></p>
20420Customer Requisition Modification01557WarehouseArmy: ASA(ALT)NewSubmitted: 6 December 2019<p><strong>Description</strong> <br /> When missing data attributes are required to be added to the Customer Profile in DPAS; if the customer due in has been generated there is NO WAY to take corrective action without a help-desk ticket. This is not effective in time management in achieving the capability of using an automatic system.</p> <p><strong>Recommended</strong> <br /> Allow the customer to modify the due-in and reprocess the same transaction after taking correction action to address the Customer Profile errors. The Customer Profile items must be aligned to Army business rules, must be mandatory fields and have drop down fields with appropriate information to allow the customer to meet Army intent.</p> <p><strong>Mission Critical</strong> <br /> This is mission critical, Army customers processed over 160 transactions (Due-in) in DPAS which currently are in a suspended state (ICP-DPAS). The customer profiles were not correctly processed with a Distribution Code (this is not a currently not a mandatory field in DPAS). This is causing delays with fielding missions in Europe.</p> <p><strong>Benefits</strong> <br /> Adding the modification process to the customer requisition (due-in) would reduce reprocessing time, improve accuracy, and accountability aligned to audit.  This would also reduce the backlog and stream line items affecting Army logistics business processes.</p> <p><strong>Users</strong> <br /> This would affect all the ASA ALT community -- users in DPAS (WM).</p>
20419DAI updates needed for CIP Process01556PADISANewSubmitted: 11/25/2019<p><strong>Description</strong> <br /> The DPAS CIP process was never set up to handle DAI fund codes.</p> <p><strong>Recommended</strong> <br /> Validations for funding cost center and major command task ID were fixed. However, we are missing more information needed to pass later validations. It's currently failing on the procedure for  uspMajor_command_project_task_Sel because of a missing agency code and major command designation code.  There is likely additional fields that will be required to bring the CIP asset into the property book.</p> <p><strong>Mission Critical</strong> <br /> Currently customers using DAI cannot access their fund codes, cost centers and more within CIP Project, and therefore cannot realize their CIP assets to book.</p> <p><strong>Benefits</strong> <br /> Users can process CIP transactions with DAI cost centers, fund cds, etc.</p> <p><strong>Users</strong> <br /> At this time, this likely is only affecting DISA users.  See TFS 46760 for additional information.</p>
20418Ammunition and Explosives Tracking01555EnterpriseArmyNewSubmitted: 20 November 2019<p><strong>Description</strong></p> <ol> <li>DPAS does not have a Net Explosive Weight (NEW) field for Ammunition and Explosives (A&E) material.</li> <li>DPAS does not have a Hazard Classification (HC) or Storage Compatibility Group (SCG) field for A&E material.</li> <li>Original Document Number is not a selectable category for creating reports.</li> <li>The Dept. of Defense Identification Code (DODIC) is not a selectable category for creating reports.</li> <li>Condition Code (CC) is not a selectable category for creating reports.</li> <li>DPAS does not have an A&E specific monthly inventory sheet.</li> <li>DPAS does not allow for decimals in the quantity field.</li> <li>Item Description gets cut off when pulling reports.</li> </ol> <p><strong>Recommended</strong></p> <ul> <li>Add the item NEW and HC/SCG to the Stock Number entry page.</li> <li>Allow for a total NEW within reports function (Quantity x NEW).</li> <li>Users should also have the ability to total the NEW for a specific storage location.</li> <li>Make all of these fields accessible categories for creating reports.</li> <li>Create a A&E specific monthly inventory sheet, with necessary information (Document Number, DODIC, NSN, Lot Number, Serial Number, Nomenclature, Condition Code, Quantity on Hand).</li> <li>Add three required signature blocks to inventory sheet (Inventory Officer, Magazine Manager, and Supervisor).</li> <li>Allow for decimal numbers to be entered into the quantity field.</li> </ul> <p><strong>Mission Critical</strong> <br />All A&E assets are required by DoD to be managed by NEW, HC/SCG.  Currently this is being done manually, which creates room for error.  The current inventories and reports within DPAS are geared towards assets other than A&E.  Quantities listed in DPAS often do not accurately reflect the actual quantity on hand.  A&E items require decimal numbers, to reflect true quantities.</p> <p><strong>Benefits</strong> <br />The benefits of implementing these solutions include all of the above, reduces time/cost and improve accuracy accountability by not having to keep a separate set of records due to quantity inaccuracies, NEW, hazard classification, and storage compatibility monitoring.  Also improves A&E safety and security by having a real-time view of storage location holdings.</p> <p><strong>Users</strong> <br />These issue affect all organizations/users managing A&E assets.</p>
20417LIMS-EV01554PAAF: OtherNewSubmitted: November 15, 2019<p><strong>Description</strong> <br /> Additional data needs to be pushed to LIMS-EV for report building capability</p> <p><strong>Recommended</strong> <br /> The data needed are Last Inventory Date/Time, FAD code, and CIIC</p> <p><strong>Mission Critical</strong> <br /> This is critical to facilitate LIMS-EV report generation and necessary for AF to identify and track COMSEC as required by Committee on National Security Systems Instruction (CNSSI) No. 4001</p> <p><strong>Benefits</strong> <br /> LIMS-EV data will be used to not only generate reports but will make DPAS data available to other systems (i.e. DRRS) through LIMS-EV instead of DPAS interface</p> <p><strong>Users</strong> <br /> This change will affect all users within our SiteID</p>
20416DPAS Diagnostics Screen01553EnterpriseLeidosDoneSubmitted: 11/14/2019<p><strong>Description</strong> <br /> With the upcoming addition of RabbitMQ to DPAS, there needs to be a screen that the DevSecOps group can use to test that the server is up, responding and is properly configured.</p> <p><strong>Recommended</strong> <br /> Add a screen to the Administration module that will perform diagnostic checks against the RabbitMQ instance.</p> <p><strong>Mission Critical</strong> <br /> Yes.  Without the new process, there is not good method for accessing RabbitMQ.</p> <p><strong>Benefits</strong> <br /> The DPAS development teams ability to monitor and confirm that a server is up and properly configured will improve our response time during outages, and our confidence in the health of our production infrastructure.</p> <p><strong>Users</strong> <br /> This screen will only change the Administration console and should have no impact on non-administrative users.</p> <p><strong>Completed – Release 7.2.10 – 22 November 2019</strong></p>
20415CAGE Cd and MAJ Cmd Cd add to Asset Inquiry01552PAAF: GEITNewSubmitted: 11/7/2019<p><strong>Description</strong> <br /> The Asset Inquiry selectable fields do not allow for selection of CAGE Code or Major Command Code.  Our users are unable to generate an inquiry report with these fields.  This inhibits our users from generating reports needed for day-day operations and research. </p> <p><strong>Recommended</strong> <br /> Recommend adding the CAGE Cd and Maj Cmd Cd fields to the field selection table under  Inquiries/Asset Management/Asset.</p> <p><strong>Mission Critical</strong> <br /> Yes, all users in FF-GEIT will require these fields for inquiries on a daily basis.  CAGE Cd is used to identify where equipment was manufactured and MAJ Cmd Cd separates equipment into the Major Commands that equipment belongs to.  SAF requires mandatory reports based on MAJCOM and CAGE Cd on a regular basis.</p> <p><strong>Benefits</strong> <br /> This solution will provided the ability to create reports for financial reporting and research at the MAJCOM level.  Without this information, MAJCOM equipment custodians cannot accurately or efficiently perform their duties.</p> <p><strong>Users</strong> <br /> Yes, this will affect all APOs and PAs, which is all users within FF-GEIT.</p>
20414LMP Interface01551PAArmyDoneSubmitted: 30 Oct 2019<p><strong>Description</strong> <br /> Currently X807 to LMP outbound file for receipt by LMP for not being received depreciation transactions.</p> <p><strong>Recommended</strong> <br /> Add X807 to outbound transactions for Accounting Interface LMP with proper codes.</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong> <br /> Financial Reporting</p> <p><strong>Users</strong> <br /> Yes</p> <p><strong>Completed – Release 2020.2 – 26 June 2020</strong></p>
20413Over ride inspection with meter reading01550WarehouseAF: AFERMSDoneSubmitted: 30 Oct 19<p><strong>Description</strong> <br /> We have space suits that come due based on a calendar interval or a meter reading, which ever comes first.</p> <p><strong>Recommended</strong> <br /> We need ability to set an override on an inspection due date with a meter reading, set at the NSN level. </p> <p><strong>Mission Critical</strong> <br /> critical</p> <p><strong>Benefits</strong> <br /> time savings. currently using manual entries to figure out inspection cycles. </p> <p><strong>Users</strong> <br /> All AFERMS</p> <p><strong>Completed – Release 2020.3 – 9 October 2020</strong></p>
20412Batch Container Movement01549WarehouseAF: AFERMSDoneSubmitted: 30 Oct 19<p><strong>Description</strong> <br /> Currently in order to move a container, you have to move a container one at a time. We need the ability to move multiple containers at the same time to a new location. During this process nothing else but move location should be able to happen</p> <p><strong>Recommended</strong><br /> be able to select multiple containers and move them all at the same time</p> <p><strong>Mission Critical</strong><br /> critical</p> <p><strong>Benefits</strong><br /> time savings. currently using container edit and moving one at a time </p> <p><strong>Users</strong><br />All AFERMS</p> <p><strong>Completed – Release 2020.1 – 6 March 2020</strong></p>
20411Inventory Signature Block01548PAAF: GEITNewSubmitted: 2019 Oct 25<p><strong>Description</strong> <br /> Property Administrators are unable to change signature blocks when generating equipment inventories.</p> <p><strong>Recommended</strong> <br /> Recommend Property Administrators be give the ability to modify signature blocks generated on inventory reports.</p> <p><strong>Mission Critical</strong> <br /> Yes, AFMAN 17-1203 requires the APO and individuals performing inventories to sign inventory reports when inventories have been accomplished.  DPAS does not provide the capability for Property Administrators to update inventory signature blocks before generating inventory reports.  Without the appropriate signatures on an inventory, the report cannot meet AFMAN requirements.</p> <p><strong>Benefits</strong> <br /> This solution will provide a finished product when an Property Administrator generates a report.  Currently, the Property Administrator has to pulled down a report and then add signature blocks with the correct information in a PDF format.  Auto-generating the report with signature blocks already formatted correctly and attached will save time and confusion for property administrators and ensure accurate documentation of inventory actions IAW AFMAN 17-1203.</p> <p><strong>Users</strong><br /> This will affect all FF-GEIT DPAS Users. </p>
20410AUIC all Pending Transaction Lookup01547PAAF: GEITNewSubmitted: 2019 Oct 25<p><strong>Description</strong> <br /> Property Administrators (PA) cannot view pending transactions for all UICs underneath their assigned AUIC.  They must change the UIC to view pending transactions at each UIC.  Would like to give PAs the ability to view all pending transaction under their assigned AUIC without having to log into each UIC individually.</p> <p><strong>Recommended</strong> <br /> Create the capability for PAs to view all pending transactions for every UIC underneath the AUIC they are assigned.  Eliminate the need to log in to each UIC individually to see pending transactions.</p> <p><strong>Mission Critical</strong> <br /> This is not mission critical at this time.  However, it is very time consuming and inconvenient for the PA to change UICs if they want to view all pending transactions within their AUIC.</p> <p><strong>Benefits</strong> <br /> This solution will save time and prevent confusion for PAs.  PAs manage all UICs within their assigned AUIC, therefore they need the ability to monitor all UICs without having to switch continuously.</p> <p><strong>Users</strong> <br /> This will affect all PAs assigned to FF-GEIT.</p>
20409Inventory By Exception Upload01546PADIANewSubmitted: 10/9/2019<p><strong>Description</strong> <br />We should be able to import spreadsheets or data files into the Inventory module in Property Accountability to mark items as inventoried. The spreadsheets would be populated by network scanning or other tools, not DPAS AIT scanners.</p> <p><strong>Recommended</strong> <br />Develop a template and a process to import inventory results from something other than an AIT scanner</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong> <br />Reduce time to complete inventories and improve accountability</p> <p><strong>Users</strong> <br />Affects all users.</p>
20408Add Calendar Management role to Warehouse Tech01545WarehouseAF: AFERMSDoneSubmitted: 8 Oct 19<p><strong>Description</strong> <br /> Under warehouse Mgmt., Scheduling, Calendar Mgmt our warehouse technician has no rights. They currently can not even view as it isn't under their rights to access. </p> <p><strong>Recommended</strong> <br />We need Calendar Mgmt added to our Warehouse Technician role.</p> <p><strong>Mission Critical:</strong> <br />critical</p> <p><strong>Benefits:</strong> <br />time savings. currently we would have to set up classes as a warehouse Officer for all of our warehouses, and these classes are under constant change. </p> <p><strong>Users:</strong> <br />All AFERMS</p> <p><strong>Completed – Release 7.2.10 – 22 November 2019</strong></p>
20407DPAS Roles Addition01544WarehouseArmy: ASA(ALT)DoneSubmitted: 19 Sept 19<p><strong>Description</strong> <br /> ASA(ALT) community would like to customize roles for it's users in support of the mission objectives of the Program Managers.</p> <p><strong>Recommended</strong> <br />Create new roles to meet the requirements of the ASA (ALT) community (see attached).</p> <p><strong>Mission Critical</strong> <br />This is mission critical because ASA(ALT) PMs operate in a slightly different manner than a traditional warehouse.  We also need to have super users available to support each organization.</p> <p><strong>Benefits</strong> <br />ASA(ALT) PMs will be able to utilize and execute DPAS in accordance with their mission objectives.</p> <p><strong>Users</strong> <br />Yes</p> <p><strong>Completed – Release 7.1.32 – 04 October 2019</strong></p>
20406LIN SUB APPEN H01543EnterpriseArmy: USASOCNewSubmitted: 9/10/2019<p><strong>Description</strong> <br /> Catalog needs to cross-reference LIN/NSLIN and NSN/MCN for  authorized LIN/NSLINs when adding items to the accountable record. When an asset is receipted the LIN of the NSN of the asset is consistent but will allow substitutions based on approved substitution list and role.  During Receipt/Update/Transfer user should not be able to select LIN, LIN would default to proper LIN of NSN/MCN/Part. Keep Stock Number integrity with LIN including feed from SB 700-20 of LIN Substitutions Appendix H.  Alternate solution with keeping existing functionality create roles to limit Pending Receipt to specific roles, to use local due in for control, further testing by USASOC of functionality.</p> <p><strong>Recommended</strong> <br />LIN/NSLIN and substitution for LINs</p> <p><strong>Mission Critical</strong> <br />Yes</p> <p><strong>Benefits</strong> <br />Sub and Prime LIN associated data tracked of IN LIU of and substitution. </p> <p><strong>Users</strong> <br />Yes</p>
20405Interface with Navy ERP01542WarehouseUSMC: DMCNewSubmitted: 09/04/2019<p><strong>Description</strong> <br />The USMC is implementing Navy ERP to replace the Stock Control System (SCS) currently utilized by LOGCOM for Navy Working Capital assets.   DPAS-WM will still be the warehouse management tool for Navy ERP and will need to be able to interface with it. </p> <p><strong>Recommended</strong> <br />Create an interface/ICD with Navy ERP.  Model will be similar to SCS. </p> <p><strong>Mission Critical</strong> <br />Mission Critical.   Navy ERP does NOT manage at the serial number level (similar to SCS) and needs DPAS-WM for that capability. </p> <p><strong>Benefits</strong> <br />It keeps LOGCOM and DPAS-WM in compliance with USMC policy on Navy ERP implementation. </p> <p><strong>Users</strong> <br />Majority of Marine Forces Storage Command (MFSC) users will utilize this interface with Navy ERP. </p>
20404Reporting CICP Transactions to GFP Module01541WarehouseAF: Other {GFM-A}NewSubmitted: 14 Aug 2019<p><strong>Description</strong> <br />Air Force contractors are required to report Government Furnished Property (GFP) in their possession to the Procurement Integrated Enterprise Environment (PIEE) Government Furnished Property (GFP) Module.  Air Force Contractor Inventory Control Points (CICPs) are also required to report logistics transactions to DPAS for accountability purposes.  Currently, the CICPs accomplish this via Swivel chair/dual entry to these systems. </p> <p><strong>Recommended</strong> <br />M-A ‘Self-Service module’ (DPAS Warehouse module) to the Procurement Integrated Enterprise Environment (PIEE) Government Furnished Property (GFP) Module. </p> <p><strong>Mission Critical</strong> <br />Contractors are mandated to report Government Furnished Property (GFP) in their possession per DFARS 252.211-7007.</p> <p><strong>Benefits</strong> <br />Air Force contractors reporting the transactions to the Procurement Integrated Enterprise Environment (PIEE) Government Furnished Property (GFP) module will eliminate swivel chair/dual entry and reduce the possibility of date entry errors.  In addition, elimination of dual entry will allow the Air Force program offices to avoid this cost.</p> <p><strong>Users</strong> <br />ALL AF GFM-A users</p>
20403AFWay/DPAS Interface via GEX01540PAAF: GEITDoneSubmitted: 20190814<p><strong>Description</strong> <br />AFWay is unable to communicate with the DPAS "AFWay IT Custodian Access" web service.</p> <p><strong>Recommended</strong> <br />Update the process to provide the same information via DAAS Gex folders.  Data will be provided once daily via a scheduled job.  The output of which will be loaded to GEX for ftp to AFWay.</p> <p><strong>Mission Critical</strong> <br />The information that will be pulled from DPAS is critical to validate purchasing privileges within AFWay. This access management control is essential in ensuring only specific personnel may purchase IT assets from AFWay, the primary procurement vehicle for IT assets within the Air Force. The lack of a properly functioning interface between DPAS and AFWay inhibits the Air Force's ability to control IT spend across the enterprise.</p> <p><strong>Benefits</strong> <br />This solution will automate the process of consuming DPAS information into AFWay Database, which will save time, increase data accuracy, and increase asset accountability.</p> <p><strong>Users</strong> <br />This will affect all AFWay Users within and outside its (AFWay) component/agency. </p> <p><strong>Completed – Release 2020.1.2 – 17 April 2020</strong></p>
20402Serial Number Sorting in DPAS01539PAAF: GEITNewSubmitted: 9 Aug 2019<p><strong>Description</strong> <br />During recent transactions in DPAS, we found that assets do not come up in serial number order. This is causing issues when transferring of assets, especially if the transfer involves multiple assets, as you have to search through all of the assets listed under a custodian number to find the assets that need to be transferred. This is not just limited to transfers.</p> <p>Currently, assets come up by stock number. Serial numbers and asset IDs are presented in no order. Having assets come up in serial number order will lessen the time it takes to process a transaction in DPAS and put less strain on manpower.</p> <p><strong>Recommended</strong> <br />Add the capability to sort assets throughout DPAS by Serial Number order.</p> <p><strong>Mission Critical</strong> <br />Yes.  Property Administrators are spending large amounts of time searching for serial #s throughout DPAS.  Having them in serial number order will simplify searching on DPAS screens by giving users a quick look in numeric order.</p> <p><strong>Benefits</strong> <br />Having assets come on screen in serial number order will simplify searching on DPAS screens by giving users a quick look in numeric order.  This will reduce the amount of time it takes a property administrator to find an asset on a screen.</p> <p><strong>Users</strong> <br />Yes, the ability to look at assets in serial number order will assist all users in navigating DPAS screens/functions.</p>
20401Addition of UIC to Manufacturer/Asset Inquiry selectable fields01538PAAF: GEITRemovedSubmitted: 8 Aug 2019<p><strong>Description</strong> <br />To perform Catalog Management tasks additional inquiry fields are needed in the field selection table under Inquires-Asset Management-Manufacturer/Asset. Propose adding "UIC" to selectable fields.</p> <p><strong>Recommended</strong> <br />Add "UIC" to select fields under Inquiries-Asset Management-Manufacturer/Asset.</p> <p><strong>Mission Critical</strong> <br />Yes.  As Air Force Equipment Control Officers (Catalog Managers), these fields are needed when building, grouping, and researching reports used for Catalog Management.  Catalog Managers cannot look up asset information by UIC to find users that are using erroneous catalog entries.</p> <p><strong>Benefits</strong> <br />Enables Catalog Managers to create reports tailored to performing research for cleaning up the current FF-GEIT catalog. Enables users to create reports tailored to key fields of data used to identify and sort assets within FF-GEIT.  Addition of the UIC field to the Asset Management-Manufacturer/Asset inquiry selectable fields will enhance accountability of 2.7M assets for over 900 equipment control officers maintaining asset readiness at over 300 locations world-wide.</p> <p><strong>Users</strong> <br />Yes, the ability to perform research for catalog updates/cleansing enables all DPAS users to select from verified catalog entries when complete.</p> <p><strong>25 Sept 2019 – cancelled per MSgt Christopher Seim </strong> <br /> close out the SCR…the method you suggested meets our requirement.</p>
20400Addition of Manufacturer Part Number to Asset Inquiry selectable fields01537PAAF: GEITNewSubmitted: 8 Aug 2019<p><strong>Description</strong> <br />To perform inquiries and generate reports necessary for daily IT Asset Management tasks additional inquiry fields are needed in the field selection table under Inquires-Asset Management-Asset. Propose adding "Manufacturer Part Number" to selectable fields.</p> <p><strong>Recommended</strong> <br />Add "Manufacturer Part Number" to select fields under Inquiries-Asset Management-Asset.</p> <p><strong>Mission Critical</strong> <br />Yes.  As Air Force Equipment Control Officers and Base Equipment Control Officers, these fields are needed when building, grouping, and sorting reports.</p> <p><strong>Benefits</strong> <br />Enables users to create reports tailored to key fields of data used to identify and sort assets within FF-GEIT.  Addition of the Manufacturer Part Number field to the Asset Inquiry will enhance accountability of 2.7M assets for over 900 equipment control officers maintaining asset readiness at over 300 locations world-wide.</p> <p><strong>Users</strong> <br />Yes, all users within FF-GEIT will require these fields when performing asset inquiries.  They are available on other inquiry screens, but not this one.</p>
20399Manage SKO ability to correct ICN information during a QC01536WarehouseAF: AFERMSDoneSubmitted: 5 Aug 19<p><strong>Description</strong> <br /> We can QC/QA/Inspection an item that is ready for a relook, but cannot use SKO Manage to update components that were found incorrect during the QC. We can use the SKO Manage to change out an item as it brings up part of the ICN information. But if there is a narrative that documentation is incorrect, you have to go to inventory manager and remove the item, edit the information, reinstall the item, then go back to QC to put corrective action in, but can't because inventory can't be found error pops. At this point a help ticket is put in so a script can be run to fix the error. </p> <p><strong>Recommended</strong> <br /> allow update of ICN information in SKO Manage block, see power point explaining</p> <p><strong>Mission Critical</strong> <br /> critical</p> <p><strong>Benefits</strong> <br /> time savings. currently we would have to sign off the QC without fixing the information. Then fix the information and re QC it. Will help keep desk tickets down. </p> <p><strong>Users</strong> <br />All AFERMS</p> <p><strong>Completed – Release 2020.1 – 6 March 2020</strong></p>
20398Physical Inventory Inquiry01535WarehouseUSMC: CSPDoneSubmitted: 2 Aug 2019<p><strong>Description</strong> <br />Currently it is very difficult to locate the last Table of Authorized Material Control Number (TAMCN) or Stock Number inventory date.   Unless the user has manually recorded the Physical Inventory number for every TAMCN and Stock Number as they complete,  there is no simple way to locate that information within DPAS.  As part of our annual FISCAM audit process, the auditors request of the last inventory dates of selected TAMCN and stock numbers.   Without this capability, it is very difficult to meet this audit requirement. </p> <p><strong>Recommended</strong> <br />Recommending that a Physical Inventory Inquiry by enterprise level be created to make researching when the required physical inventories were conducted on TAMN's and Stock Numbers.  At a minimum this inquiry should have the following columns: Logistics Program, Region, Site, Warehouse, TAMN, Stock Number, Item Description, Physical Inventory Number, Expected Qty, Counted Qty, Difference Qty, Date of Inventory, User ID.  If the physical inventory required that an Inventory reconciliation to be conducted, then the Inventory reconciliation document number, the date of the reconciliation and user id should also be included in the query.</p> <p><strong>Mission Critical</strong> <br />This is mandated by FISCAM audit.  Inventory must be verified against last annual inventory date. </p> <p><strong>Benefits</strong> <br />This improves accountability and audit readiness of DPAS.  </p> <p><strong>Users</strong> <br />All IIF & UIF.  All services and entities required to undergo FISCAM audits would benefit from this SCR. </p> <p><strong>Completed -- Release 2021.2 - 28 May 2021</strong></p>
20397Additional Search fields and viewable for Inquiries01534EnterpriseAF: VSCOSNewSubmitted: 24 Jul 19<p><strong>Description</strong> <br />When doing Enterprise wide inquiries on Work Orders & Sub Work Orders not all information inputted into these are viewable or search-able by using the fields tab when setting up an Inquiry. Having to piecemeal a report together between multiple inquiries in an effort to generate required information is not taking advantage of the system capabilities and time consuming. Also, when trying to view work order inquiries for the entire Agency the Inquiry will time out (looking for too much information). This is unacceptable for Enterprise Vehicle Management.</p> <p><strong>Recommended</strong> <br />Add "Last Updated By" & "Work Order Status Cd" choices under the "Available Fields(s)" Search (build) area of Work Order and Work Order-Asset Inquires. Also, add "Return Dt" & "Work Order Est Service End Dt" to the "Fields" area will greatly enhance Enterprise Inquires and allow the system to look for a more refined Inquiry and not time out due to all the data it is looking for.</p> <p><strong>Mission Critical</strong> <br />This is critical.  Fleet managers count on viewing information to be able to make informed decisions to manage Air Force fleets around the globe to make informed/sound vehicle management decisions.</p> <p><strong>Benefits</strong> <br />Allowing all fields of a Work order to be viewed in all Inquiries will enhance reports and inquiries for all. Enabling user to search and build reports on any data fields available within the work- order and sub/worker.</p> <p><strong>Users</strong> <br />This SCR will affect the entire AF Agency, all Air Force fleet managers/maintenance controllers utilize this information for day to day fleet management operations.  </p>
20396Printer DPI Capability01533EnterpriseSOCOMNewSubmitted: 24 July 19<p><strong>Description</strong> <br />Request support of 300 DPI type printers within PA and WH modules.</p> <p><strong>Recommended</strong> <br />Enable compatibility of 300 DPI printers with DPAS.</p> <p><strong>Mission Critical</strong> <br />Mission Critical - 90% of NSW compatible printers are Zebra 430T which are 300 DPI.</p> <p><strong>Benefits</strong> <br />Reduces cost in acquisition of all new printers.</p> <p><strong>Users</strong> <br />This will affect all users that require print capability</p>
20395Centralized Work Order Creation01532MUAF: SPT EQUIPDoneSubmitted: 19 Jun 2019<p><strong>Description</strong> <br />Currently, work orders can only be opened by individuals assigned to a specific Mx Activity.  This works well for day to day operations however, as an entity, the Air Force continues to centralize operations in an effort to standardize business practices. We are requesting a feature that will allow a mass work order generation that will span all affected Mx Activities across an entire Site ID. </p> <p><strong>Recommended</strong> <br />When opening an instance of a work order utilizing Stock Number and/or CAGE Cd and/or Asset ID criteria, we would like a feature that will allow that work order to be generated  across all affected Mx Activities within a Site ID.  Also, we would like for the Work order Reason Cd, Work Order description, Work Plan Type Cd and Requested Service field to be locked down once we create a centralized work order.  This is especially important for TCTO, Service Bulletin and One-time inspection work orders.  Allowing individual users across 350+ Mx Activities to create or update these work orders, results in missed compliance suspense's and degrades reporting/analysis actions.</p> <p><strong>Mission Critical</strong> <br />This is mission critical.  Allowing individual users across 350+ Mx Activities to input specific information, especially for TCTO, Service Bulletin and One-time Inspection actions results in severely degraded data integrity and reporting. This directly affects the safety of equipment and the personnel utilizing that equipment.</p> <p><strong>Benefits</strong> <br />Improves accuracy of status reporting of support equipment for AF readiness reporting and program office sustainment planning.  Eliminates questionable status for users of the equipment.</p> <p><strong>Users</strong> <br />This SCR directly applies to the business practices that 441 VSCOS also wishing to implement for work order creation as well.  Additionally, this will benefit all DoD entities that are moving toward more centralized operations.  </p> <p><strong>Completed – Release 2020.3 – 9 October 2020</strong></p>
20394Additional Information Report01531WarehouseAF: AFERMSDoneSubmitted: 17 Jul 19<p><strong>Description</strong> <br />Currently under additional information, Information is collected for equipment such as Actuation, Batt Voltage, 5 Different Blanks, Gain, LBI, Repair Spot for example. This information is important and being tracked , but the only way to get this information is to open each and every ICN, go to selected items and click edit, and then click additional Info button to see what information was collected. </p> <p><strong>Recommended</strong> <br />Establish an "Additional Information Report" See attached example</p> <p><strong>Mission Critical</strong> <br />highly important.  it saves time and allows the user to see how many times chutes are being actuated on a stock number for example</p> <p><strong>Benefits</strong> <br />accurate and time saving reporting.</p> <p><strong>Users</strong> <br />all</p> <p><strong>Completed – Release 2020.1 – 6 March 2020</strong></p>
20393ICP Stock Item Add01530Materiel ManagementUSMC: CSPNewSubmitted: 17 July 2019<p><strong>Description</strong> <br />Currently in the ICP module when adding Stock Items to warehouses you are only allowed to select one warehouse at a time.  With 44 warehouses this is a very time consuming effort just to get one stock item added to 44 warehouses.</p> <p><strong>Recommended</strong> <br />Recommend the ability to be able to select all warehouse or select multiple Warehouses.</p> <p><strong>Mission Critical</strong> <br />Yes, This will save numerous hours of trying to get stock items loaded into the proper warehouse in a timely matter.</p> <p><strong>Benefits</strong> <br />This will save numerous hours of trying to get stock items loaded into the proper warehouse in a timely matter.</p> <p><strong>Users</strong> <br />All IIF & UIF</p>
20392Add DEPRN CD to Inventory Report01529PANavyNewSubmitted: 10 July 2019<p><strong>Description</strong> <br />Current Inventory Reports do not identify the DEPRN Cd for each asset. This information is necessary to identify if an asset is required to be inventoried annually or triennially. As a result this does not allow the user to easily identify those assets as such in the report.</p> <p><strong>Recommended</strong> <br />Include the DEPRN CD for each asset listed on the Inventory Report.</p> <p><strong>Mission Critical</strong> <br />Mandated In accordance with DoDI 5000.64 and USD (C) FIAR Guidance, the Accountable Property System of Record will be the authoritative source for validating the existence, completeness, and valuation of an asset. Records must be current and reflect the current status, value, location, condition.</p> <p><strong>Benefits</strong> <br />The benefits of implementing this change would be reduced time and cost, improvements in accuracy and accountability, and making financial reporting more efficient.</p> <p><strong>Users</strong> <br />This with affect ALL users.</p>
20391Edit Issued Items01528WarehouseUSMC: CSPNewSubmitted: 09 July 2019<p><strong>Description</strong> <br />Currently there is no functionality to be able to edit an issued item, Example Serial Number, Manufacture Contract, Lot or Date or other data.</p> <p><strong>Recommended</strong> <br />Recommend that the functionality be developed to be able to edit the serial Number, Manufacture Contract, Lots and Dates or other data of issued items. </p> <p><strong>Mission Critical</strong> <br />Yes, having the functionality to be able to edit Serial Numbers, Manufacture Contract, Lot's and Dates or any other data that is in an issue status will help improve the overall inventory posture.</p> <p><strong>Benefits</strong> <br />Having this functionality to be able to edit Serial Numbers, Manufacture Contract, Lot's and Dates or any other data that is in an issue status will help improve the overall inventory posture.</p> <p><strong>Users</strong> <br />All IIF & UIF</p>
20390Unit Outstanding Column Added01527WarehouseUSMC: CSPNewSubmitted: 9 July 2019<p><strong>Description</strong> <br />Currently there is no UIC Name Column in Inquiries>Unit Issue>Outstanding Items Inquiry.</p> <p><strong>Recommended</strong> <br />Recommend that the UIC Name Column be added to Inquiries>Unit Issue>Outstanding Items Inquiry.</p> <p><strong>Mission Critical</strong> <br />No, but having this functionality will make it easier for us to determine what warehouse and regions these Unit outstanding items belong to.</p> <p><strong>Benefits</strong> <br />Having this functionality will make it easier for us to determine what warehouse and regions these Unit outstanding items belong to.</p> <p><strong>Users</strong> <br />All IIF & UIF</p>
20389Publication Tab added to the Details Tab on an assets' Maintenance Asset Master record01526MUAF: VSCOSNewSubmitted: 3 Jul 2019<p><strong>Description</strong> <br />Currently, the way to document a publication for an asset is in the Property Accountability module and you complete this by the assets National Stock Number. This cannot be seen anywhere within the Maintenance & Utilization module. There needs to be a location in the Maintenance & Utilization module to add publications for an asset that can be viewable when creating/updating work orders and be viewable in all Asset Inquires.</p> <p><strong>Recommended</strong> <br />Create a Publication tab to the Maintenance Asset Master(MAM) record for all assets. This will be under the Details Tab of the asset. The fields will be similar to the PA module (Publication Nbr, Publication Title, and Publication Date fields) currently. With enough room to add multiple numbers and titles as needed. The publication information will be updated when profiling an asset and can be updated at anytime. This Publication Tab will also be viewable on a Work Order after the Asset Id is selected. These fields will be able to be selected to view in all Asset Inquiries in M&U as well.</p> <p><strong>Mission Critical</strong> <br />This is critical.  Fleet managers count on viewing all of an assets information to be able to make informed decisions to manage Air Force fleets around the globe.</p> <p><strong>Benefits</strong> <br />Allowing publications to be viewed in the MAM, Work Orders, and Inquiries will enhance DPAS M&U usage for all. Enabling users to be able to find relative maintenance information on a asset during it's life cycle. This will also aid in asset data integrity.</p> <p><strong>Users</strong> <br />This SCR will have a mission enhancement for all DPAS MNU users who provide maintenance support day to day.  </p>
20388CPL Dashboard01525PADISANewSubmitted: 28 Jun 2019<p><strong>Description</strong> <br />Provide the ability for Component Property Leads (CPLs) to login to a user dashboard in order to view the roll-up metrics for their component. CPL's should be able to quickly see how they are complying with DoD requirements. The dashboard would show the components last inventory by years (1, 2, 3, older than 3 years), total assets marked as GFP, Assets flagged as capital but not activated for depreciation.</p> <p><strong>Recommended</strong> <br />Establish a CPL dashboard login similar to the customer portal where hand receipt holders can view their hand receipt. The CPL will be able to only view the metric's for their component (i.e. Army, Navy, Air Force, DISA). The metrics should compile all site-id's under a component.</p> <p><strong>Mission Critical</strong> <br />This will provide the CPL's with the level of business intelligence to determine how well they are complying with DoD mandates and identify issue areas without relying on manual reporting.</p> <p><strong>Benefits</strong> <br />Provides the CPL's the ability to identify data anomalies and issue areas for corrective action. This would improve the data reliability and audit readiness of each component within DPAS.</p> <p><strong>Users</strong> <br />This would affect only the CPL's that are appointed in writing by each Component/Agency.</p>
20387Updates for Audit Readiness01524WarehouseAF: USAFANewSubmitted: 20190625<p><strong>Description</strong> <br />USAFA requires additional updates to the Issue, Return, Inquiry, and Member Profile processes to increase the efficiency and accuracy of inventory sales for audit readiness.</p> <p><strong>Recommended</strong> <br />Provide the ability to:</p> <ul> <li>Excluding specific members or groups of members from being billed</li> <li>Adding pricing information into the inquiries to look up potential charges</li> <li>Displaying cost information before a sale is complete (both issue and returns)</li> <li>Displaying cost information on the Issue/Return Receipts</li> <li>Printing “Cash Issue” on the Issue Receipt if the issue was designated as a cash issue</li> <li>Capturing Payment information for Cash Issues and returns that can be researched and exported at a later date</li> </ul> <p><strong>Mission Critical</strong> <br />This is mission critical. DPAS currently does not capture Payment information for cash issues nor does it provide the capability to query transactions that were paid by the member.  This leads to a gap in our audit readiness when USAFA needs to match a money order or transaction to an issue or return in DPAS.<br />There is also no way to calculate the total cost of a sale before the sale has been completed—we require cadets to provide a money order to cover the cost if they are not able to be billed. The cost must be known ahead of time.</p> <p><strong>Benefits</strong> <br />Implementing the proposed changes will reduce the time/cost and increase pricing accuracy for each member paid issue or return. It will also reduce the time/cost of audit research, increase the accuracy of our audit research, and produce the financial reporting that we require for our audits.</p> <p><strong>Users</strong> <br />All users</p>
20386Point Assets to Mx Activities at Asset Level01523PAAF: VSCOSNewSubmitted: 25 June 2019<p><strong>Description</strong> <br />Currently, when an asset is loaded in PA, it is assigned to one Mx Activity by Maint Grp Id via the Maint Mgmt Assign.  This means that all assets assigned to a specific UIC can only be pointed toward one specific Mx Activity only.  However, we need the capability to have assets assigned to one main UIC but have the option to point to several different Mx Activities when mission dictates.</p> <p><strong>Recommended</strong> <br />Recommend adding a feature to point assets to a specific Mx Activity at the asset level.  There are many AF units that are responsible for their assets on one property book (UIC) however, the assets are often spread across several different bases.  This creates a situation where we are forced to give bases access to several Mx Activities or have bases manually pass work order information to the base that the asset officially resides on.</p> <p><strong>Mission Critical</strong> <br />This is mission critical.  Having the work order maintenance history on all assets directly affects the assets life cycle, vital to projecting asset replacements.</p> <p><strong>Benefits</strong> <br />This change will vastly reduce time as it relates to work order reporting and accurately depict the assets operation and maintenance costs needed for projecting an assets end of life.</p> <p><strong>Users</strong> <br />The entire Air Force component as well as other services will benefit from accurate Mx Activity assignment.</p>
20385Stock Item Update01522WarehouseAF: VSCOSNewSubmitted: 24 Jun 2019<p><strong>Description</strong> <br />Improve process of loading stock numbers to warehouse sites. After a user is done loading a new stock number to the Logistics Catalog, they have to switch to the Stock Item tab to load the stock number to the their warehouse. </p> <p><strong>Recommended</strong> <br />Recommend having a "prompt box” asking the user if they want to add the new stock number to their stock item list. When the customer selects "Yes", the system is directed to the Add Stock Item window for the user to add the Stock Number to their Warehouse.  Also, consider adding a tab to the Add Stock Item window for the user to program Location Condition Code Defaults.</p> <p><strong>Mission Critical</strong> <br />Efficiently loading stock numbers is mission critical to expediting parts orders for mission generating vehicles that support launching aircraft and other air force base support functions.</p> <p><strong>Benefits</strong> <br />These changes will help speed up the Stock Number load process. The combination of three different transactions into one will also reduce transaction time.</p> <p><strong>Users</strong> <br />The entire Air Force component as well as other services will benefit from a faster way to associate Stock Numbers to their Warehouses.</p>
20384Modify Materiel Control Officer Role01521WarehouseAF: VSCOSNewSubmitted: 24 Jun 2019<p><strong>Description</strong> <br />Recommend updating Materiel Control Officer Role by adding "R" to Report Manager under Program ID: LPWHR82 "Inventory Over Under".</p> <p><strong>Recommended</strong> <br />Adding the report will assist users to increase or decrease their inventory levels as needed and aid users with future order demand decisions.</p> <p><strong>Mission Critical</strong> <br />AFI 24-302 mandates Materiel Control to monitor stock items parameters based on demand. </p> <p><strong>Benefits</strong> <br />The ability to manage stock levels based on demand will ensure availability of essential items and reduce waste allowing managers to make fact-based funding allocations. </p> <p><strong>Users</strong> <br />The entire Air Force component as well as other services will benefit from having the ability to analyze on-hand quantities and adjust replenishment parameters.</p>
20383Add Software Version field in M&U01520MUAF: SPT EQUIPNewSubmitted: 21 June 2019<p><strong>Description</strong> <br />DPAS M&U does not have a data field specifically for software version numbers.  This is a requirement for configuration control of automated test systems (ATS) and verification of ATS software version prior to performing certain operations.</p> <p><strong>Recommended</strong> <br />Add (to M&U) a new field or the ability to designate an existing field for dedicated use as Software Version field.  Field must be able to be part of an inquiry for NSN, Part Number, Serial Number, or Asset ID, with the Software Version value being returned as part of the inquiry.</p> <p><strong>Mission Critical</strong> <br />This is mission critical.  However, a dedicated field is not critical.  We need a field to document software version that is retrievable upon inquiry, that we can retain for future use. </p> <p><strong>Benefits</strong> <br />Improved configuration control and Operational Safety, Suitability and Effectiveness, ATS/Weapon System cyber-security, and more accessible information for verification prior to performing certain critical tasks.</p> <p><strong>Users</strong> <br />Only certain users - ATS users and those documenting maintenance on aircraft maintenance ATS.</p>
20382Inventory Over Under Report Modification01519WarehouseAF: VSCOSNewSubmitted: 24 Jun 2019<p><strong>Description</strong> <br />Recommend adjusting the Warehouse Module "Inventory Over Under" report by adding consumable outcome parameters (12 month increments).</p> <p><strong>Recommended</strong> <br />Adding fields with measurable data will assist users to increase or decrease their inventory levels as needed. By adding "Item Quantity Used in Last 12 Months"; "Item Quantity Backordered in Last 12 Months"; and "Recommended Adjustment" fields to the "Inventory Over Under" report will assist users with managing replenishment parameters programming and future order demand decisions.</p> <p><strong>Mission Critical</strong> <br />AFI 24-302 mandates Materiel Control to monitor stock items and adjust replenishment parameters based on demand. </p> <p><strong>Benefits</strong> <br />The ability to manage stock levels based on demand will ensure availability of essential items and reduce waste allowing managers to make fact-based funding allocations. </p> <p><strong>Users</strong> <br />The entire Air Force component as well as other services will benefit from having the ability to analyze on-hand quantities and adjust replenishment parameters.</p>
20381MISC ADD01518WarehouseUSMC: CSPNewSubmitted: 21 June 2019<p><strong>Description</strong> <br />Currently in the DPAS-WM there is no way to associate a Physical Inventory Number to a MISC Add transaction.</p> <p><strong>Recommended</strong> <br />Recommend that a Reason Desc box be added to the Misc Add process so we are able to add the Physical Inventory number.  </p> <p><strong>Mission Critical</strong> <br />Yes, Having this functionality will help us be able to associate the Physical Inventory Number to the MISC Add process helping with overall Audit Readiness. </p> <p><strong>Benefits</strong> <br />Having this functionality will help us be able to associate the Physical Inventory Number to the MISC Add process helping with overall Audit Readiness and save man hours and trying to find this data. </p> <p><strong>Users</strong> <br />All IIF/UIF</p>
20380Parts Receive Date01517WarehouseAF: VSCOSNewSubmitted: 25 April 2019<p><strong>Description</strong> <br />The DPAS M&U module does not populate the Part Receive Dt for items issued from Warehouse. M&U allows the user to enter a Part Receive Dt once part requests are established and this date is transferred over to the Maint Issue Inquiry in Warehouse. The Part Receive Dt from M&U is incorrect information for the Maint Issue Inquiry since this field should display the date parts were received into the Warehouse.</p> <p><strong>Recommended</strong> <br />We recommend that M&U auto populates the Part Receive Dt field in the sub-work order parts tab with the date that the parts are issued from the Warehouse. This field should still be editable for the user to change. If necessary, this field can be renamed to Part Issue Date to prevent any confusion. <br />In Warehouse, the Maint Issue inquiry needs to display the date that parts are received into the Warehouse. Backordered parts need to be monitored and should update their status accordingly in the Maint Issue inquiry. The backorder date is currently updated when the part enters this status but the Estimated Deliver Dt is not updating in this inquiry and the user is unable to change it once the Due-In is created. The user needs the ability to update the Estimated Delivery Dt for backordered items and these dates need to reflect in the Maint Issue inquiry. Lastly, the Part Receive Dt needs to update in the Maint Issue inquiry to reflect the date that  the parts are received into the Warehouse.</p> <p><strong>Mission Critical</strong> <br />AFI 24-302 mandates that Materiel Control initiates, monitors and follows up on part requests.  This AFI also mandates that Materiel Control checks and verifies the need for backordered parts (non-mission capable & delayed) daily.</p> <p><strong>Benefits</strong> <br />Having receipt/issue dates in M&U will provide better accountability of parts issued to work orders. In Warehouse, having correct estimated delivery and received dates will provide status accuracy and reduce research time since all information will display in one inquiry.</p> <p><strong>Users</strong> <br />The entire Air Force component as well as other services will benefit from having accurate receive dates for items in M&U and Warehouse.</p>
20379Green Procurement Program01516WarehouseAF: VSCOSNewSubmitted: 25 April 2019<p><strong>Description</strong> <br />DOD established a Green Procurement Program that gives preference to EPA-designated recycled-content vehicular products and United States Department of Agriculture-designated bio-based products. Vehicle Management is required to maintain a log of all Green Procurement purchases.</p> <p><strong>Recommended</strong> <br />Recommend adding features to receiving process to collect information needed to create a Green Procurement Report in the DPAS Warehouse. We suggest adding a "Green Procurement" check-box to the receiving process for users to identify items that fall under this criteria. The system should have an extra window during the receiving process or extra fields in the verification window for items identified as "Green Procurement" products. The extra fields need to capture the following information:</p> <ul> <li>Product Category: Drop-down options should be (Sorbent, Tire, Coolant, Engine Oil, Gear Oil, Hydraulic Fluid, and Other Lubricants)</li> <li>Product Type: Drop-down options should be (New/Virgin, Re-Refined, Recycled, Bio-Based, or Retreated) <br />Procurement Exception: Drop-down options should be (None; Excessive ETA; Manufacture Requirement; No Bio/Recycled Material; Retread Not Available Locally; Spacecraft/Launch Support; Tactical Asset; T.O. Exception; Mission Essential Support; Unreasonable Cost; Other)</li> <li>Size: Open field for user to enter Tire Size</li> </ul> <p>All the information collected along with other fields need to be combined into a Green Procurement Report. The report needs to list all historical acquisition records for items that fall under this criteria with the ability to filter by different tier levels. The report should display the following fields: Date, Product Category, Product Type, Document Type, Document Sub Type, Procurement Exception, Quantity, Unit of Issue, Stock Number, Size, Total Cost.</p> <p><strong>Mission Critical</strong> <br />Yes. The use and documentation of Green Procurement Items is mandated by the United States Environmental Protection Agency; Section 6002 of the Resource Conservation and Recovery Act (RCRA)</p> <p><strong>Benefits</strong> <br />This system upgrade will centralize Green Procurement information in one place and it will satisfy EPA requirements for all DPAS users. Also, users will no longer have to log/track GPP information using other local trackers and therefore save time/man hours.</p> <p><strong>Users</strong> <br />The entire DoD will benefit from having Green Procurement data centralized in the Warehouse Module.</p>
20378Physical Inventory Selection Improvement Location01515WarehouseAF: VSCOSNewSubmitted: 25 April 2019<p><strong>Description</strong> <br />During the Physical Inventory process when selecting a single facility, the quick search does not default to the zones and locations built within selected facility.  All zones and locations are shown regardless of facility selected. This makes it difficult with selecting specific zones if the zone names are labeled with the same name.</p> <p><strong>Recommended</strong> <br />We recommend progressive restriction for facility selections.  Example: If Facility A is selected, allow only zones, locations, containers built within Facility A to be listed as selection options.</p> <p><strong>Mission Critical</strong> <br />This is critical because we utilize zones to manage programs that exists in different facilities and have the same Zone ID.</p> <p><strong>Benefits</strong> <br />Filtering down selection options based on upper level will save time when creating new location inventories.</p> <p><strong>Users</strong> <br />The entire Air Force component as well as other services will benefit from filtering down location options based on upper level selections.</p>
20377Improve Pop-Up Windows01514WarehouseSPECWARCOMNewSubmitted: 10/03/2018<p><strong>Description</strong> <br /> There are multiple processes that have pop-up windows that are part of the functionality in order to complete each step. The size of the pop-up window is currently set at a default size and there is no option to enlarge. Require the ability to maximize the pop-up window.</p> <p><strong>Recommended</strong> <br /> Create a maximize icon at the top right corner next to the exit screen icon, allowing user to manipulate the screen with easy. This will prevent user scrolling up and down on the wrong window.</p> <p><strong>Mission Critical</strong> <br /> Mission Critical - Due to Maintenance requirement mandate. Maintenance assessments and repairs must be accomplished in accordance with current standards required by NAVSEASYSCOMINST 8370.2D and COMNAVSPECWARCOMINST 8020.2A. Maintenance assessments are required prior to SEAL/SB Team deployment. The IDTC time-line does not allow wholesale asset turn-in for maintenance. Assessments and repairs must be conducted while assets remain in SEAL/SWCC OICs/AOICs custody. Assessment results and repair parts usage must be documented when assets are not in the custody of the accountable armory.</p> <p><strong>Benefits</strong> <br /> This will allow NSW Armories to maintain their current operational level of support with minimal impact to the amount of time it takes to perform COMNAVSEASYSCOM and COMNAVSPECWARCOM required armory maintenance actions.</p> <p><strong>Users</strong> <br /> This currently applies to Armory users within NSW, but it is foreseeable that it could be applied to other departments within the command at a later date.</p>
20376All Functionality01513WarehouseSPECWARCOMNewSubmitted: 03/21/2018<p><strong>Description</strong> <br /> After user executes a 'my query', any time a filter is applied or changed within the grid, the 'my query' originally selected defaults back to the standard default grid view.</p> <p><strong>Recommended</strong></p> <ol> <li>Allowing those using a 'my query' be able to apply different filters within their query to complete their current task at hand.</li> <li>When the user cancels out their filter do not allow the 'my query' to disappear and have the standard grid options reappear.</li> </ol> <p><strong>Mission Critical</strong> <br /> Mission Critical - The user is having to stop what they were doing in order to get back to their saved query which is causing more time wasted rather then completing the task to meet their mission at hand.</p> <p><strong>Benefits</strong> <br /> This will allow NSW Armories to maintain their current operational level of support with minimal impact to the amount of time it takes to complete their task.</p> <p><strong>Users</strong> <br /> This currently applies to Armory users within NSW, but it is foreseeable that it could be applied to other departments within the command at a later date.</p>
20375Improve Unit Return01512WarehouseSPECWARCOMNewSubmitted: 10/03/2018<p><strong>Description</strong> <br /> The Unit Return Search Criteria does not allow user to search by Item Description. Armory users may not have the stock number on hand or may have multiple of that item.</p> <p><strong>Recommended</strong> <br /> Include the Intellisense Item Description field in the Search Criteria for users to during a Unit Return.</p> <p><strong>Mission Critical</strong> <br /> Mission Critical - Accountability must be accomplished in accordance with current standards required by NAVSEASYSCOMINST 8370.2D and COMNAVSPECWARCOMINST 8020.2A. Maintenance assessments are required prior to SEAL/SB Team deployment. The IDTC time-line does not allow wholesale asset turn-in for maintenance. Assessments and repairs must be conducted while assets remain in SEAL/SWCC OICs/AOICs custody. Assessment results and repair parts usage must be documented when assets are not in the custody of the accountable armory.</p> <p><strong>Benefits</strong> <br /> This will allow NSW Armories to maintain their current operational level of support with minimal impact to the amount of time it takes to perform COMNAVSEASYSCOM and COMNAVSPECWARCOM required armory maintenance actions.</p> <p><strong>Users</strong> <br /> This currently applies to Armory users within NSW, but it is foreseeable that it could be applied to other departments within the command at a later date.</p>
20374"Select All" Functionality01511WarehouseSPECWARCOMNewSubmitted: 03/21/2018<p><strong>Description</strong> <br /> Allow user the ability to add their preferred Items per page within their 'My Queries'. Also, allow the ability to be able to 'Select All' as one "items per page" options.</p> <p><strong>Recommended</strong></p> <ol> <li>Add option to default the number of assets viewed on one page within the Grid Options under "My Queries"</li> <li>Provide an option to "view all" assets within one page.</li> </ol> <p><strong>Mission Critical</strong> <br /> Mission Critical - Being able to complete a task/process without having to spend mission essential time on loading pages of assets with the desired number of items per page.</p> <p><strong>Benefits</strong> <br /> This will allow NSW Armories to maintain their current operational level of support with minimal impact to the amount of time it takes to complete their task. Commands have anywhere to 1,000-60,000 assets in their inventory. Being able to have the option to "view all" assets on one screen will cut their process time down dramatically in order to meet their mission. Having the option to have the number of items defaulted onto screen is another improvement with meeting their mission.</p> <p><strong>Users</strong> <br /> This currently applies to Armory users within NSW, but it is foreseeable that it could be applied to other departments within the command at a later date.</p>
20373Improve Unit Return01510WarehouseSPECWARCOMNewSubmitted: 10/03/2018<p><strong>Description</strong> <br /> During a Unit Return, the assets are populated and user has the option to arrange the column in ascending or descending alphabetical or numerical order. When selecting the serial number to arrange in order then selecting the stock number to arrange in order, the serial number reverts to previous setting of not being in order. DPAS should allow user to select primary and secondary sorting or simply sort by stock number then sub-sort by serial.</p> <p><strong>Recommended</strong> <br /> Allow the sorting option to work similar to the way Microsoft Excel's column filter option operates. By first selecting the serial number column and arranging it in order, then selecting the nomenclature column to arrange in order. Which leaves the serial numbers still in order.</p> <p><strong>Mission Critical</strong> <br /> Mission Critical - Accountability must be accomplished in accordance with current standards required by NAVSEASYSCOMINST 8370.2D and COMNAVSPECWARCOMINST 8020.2A. Maintenance assessments are required prior to SEAL/SB Team deployment. The IDTC time-line does not allow wholesale asset turn-in for maintenance. Assessments and repairs must be conducted while assets remain in SEAL/SWCC OICs/AOICs custody. Assessment results and repair parts usage must be documented when assets are not in the custody of the accountable armory.</p> <p><strong>Benefits</strong> <br /> This will allow NSW Armories to maintain their current operational level of support with minimal impact to the amount of time it takes to perform COMNAVSEASYSCOM and COMNAVSPECWARCOM required armory maintenance actions.</p> <p><strong>Users</strong> <br /> This currently applies to Armory users within NSW, but it is foreseeable that it could be applied to other departments within the command at a later date.</p>
20372Improve Warehouse Activity Report01509WarehouseSPECWARCOMRemovedSubmitted: 10/03/2018<p><strong>Description</strong> <br /> Report LPWHR78 Warehouse Activity only captures the UIC. The account names are needed to identify what platoons the transactions were against. All transactions captured only contain unit's UIC and not the unit's name. Multiple units have the same UIC, creating accounts under the UIC were used to identify the platoons.</p> <p><strong>Recommended</strong> <br /> List account name next to UIC for all transactions in the Warehouse Activity Report.</p> <p><strong>Mission Critical</strong> <br /> Mission Critical - Accountability must be accomplished in accordance with current standards required by NAVSEASYSCOMINST 8370.2D and COMNAVSPECWARCOMINST 8020.2A. Maintenance assessments are required prior to SEAL/SB Team deployment. The IDTC time-line does not allow wholesale asset turn-in for maintenance. Assessments and repairs must be conducted while assets remain in SEAL/SWCC OICs/AOICs custody. Assessment results and repair parts usage must be documented when assets are not in the custody of the accountable armory.</p> <p><strong>Benefits</strong> <br /> This will allow NSW Armories to maintain their current operational level of support with minimal impact to the amount of time it takes to perform COMNAVSEASYSCOM and COMNAVSPECWARCOM required armory maintenance actions.</p> <p><strong>Users</strong> <br /> This currently applies to Armory users within NSW, but it is foreseeable that it could be applied to other departments within the command at a later date.</p> <p><strong> 11 Jun 2021 - cancelled per Gregory Gleichman </strong> <br /> There are no longer additional occurrences of where this information is not populating on the Warehouse Activity Report.</p>
20371Gray-out Condition Code01508MUAF: VSCOSRemovedSubmitted: 13 June 2019<p><strong>Description</strong> <br /> Current, M&U ability to reflect conflicting status codes (i.e. NMC and Condition Code A) will cause readiness reporting problems for AF aviation Support Equipment.</p> <p><strong>Recommended</strong> <br /> Gray-out the Condition Code drop-down for AF aviation SE users.</p> <p><strong>Mission Critical</strong> <br /> This is mission critical.  Conflicting status codes are not permitted and will cause readiness questions, particularly with nuclear certified equipment being used in nuclear operations.</p> <p><strong>Benefits</strong> <br /> Improves accuracy of status reporting of support equipment for AF readiness reporting and program office sustainment planning.  Eliminates questionable status for users of the equipment.</p> <p><strong>Users</strong> <br /> Only certain users - those documenting maintenance on aviation support equipment.</p> <p><strong> 26 Oct 2021 - cancelled per Luther Meitzner</strong><br />No longer required.</p>
20370Add Sub-work-order State Code01507MUAF: VSCOSRemovedSubmitted: 13 Jun 2019<p><strong>Description</strong> <br /> Need option added to Sub-work order State Code that reflects work orders are closed, with discrepancies carried forward to a new work order. This is necessary if a discrepancy is found during an inspection and the inspection is completed. The discrepancy would be carried forward to a new job that includes only that discrepancy.</p> <p><strong>Recommended</strong> <br /> Add "Closed, Carried Forward" option to Sub-work-order State Code drop down.</p> <p><strong>Mission Critical</strong> <br /> This is mission critical.  Most SE cannot be used if overdue inspection - we need to be able to close the inspection work order when the inspection is complete.</p> <p><strong>Benefits</strong> <br /> Improves accuracy of status reporting of support equipment for AF readiness reporting and program office sustainment planning.</p> <p><strong>Users</strong> <br /> Only certain users - those documenting maintenance on aviation support equipment.</p> <p><strong> 26 Oct 2021 - cancelled per Luther Meitzner</strong> <br /> No longer required.</p>
20369FAST Projections01506MUOSDNewSubmitted: 06 Jun 2019<p><strong>Description</strong> <br /> Fleet Cost Projections required for FAST reporting needs loading three times a year.  Would be beneficial to load entire Agency at one time.</p> <p><strong>Recommended</strong> <br /> Automate the manual Projection process in DPAS where the final numbers can be pulled at one time and loaded to FAST.  Also create a FAST Budget role for access to this functionality only.</p> <p><strong>Mission Critical</strong> <br /> Costing reporting is a mandated requirement within FAST.</p> <p><strong>Benefits</strong> <br /> Reduces time and improves data integrity if we automate in DPAS.</p> <p><strong>Users</strong> <br /> Only the DPAS user in M&U that manages fleet or fleet budget.</p>
20368mandatory component font01505WarehouseAF: AFERMSNewSubmitted: 06 Jun 2019<p><strong>Description</strong> <br /> We have numerous optional components in kits due to mission requirements. Its hard to tell which ones are mandatory</p> <p><strong>Recommended</strong> <br /> make the mandatory components a Bold font</p> <p><strong>Mission Critical</strong> <br /> important</p> <p><strong>Benefits</strong> <br /> reduces confusion</p> <p><strong>Users</strong> <br /> all</p>
20367receiving documents inquiry total price01504WarehouseAF: AFERMSDoneSubmitted: 06 Jun 2019<p><strong>Description</strong> <br /> when forecasting a budget, I need to add up all my receipts to get an estimate. currently I can find the data in the system, but not easily.</p> <p><strong>Recommended</strong> <br /> At inquiries, documents grid, add a total price column and display the total price of each document.</p> <p><strong>Mission Critical</strong> <br /> important</p> <p><strong>Benefits</strong> <br /> time savings,</p> <p><strong>Users</strong> <br /> all</p> <p><strong>Completed – Release 2020.2 – 26 June 2020</strong></p>
20366over under size column01503WarehouseAF: AFERMSNewSubmitted: 06 Jun 2019<p><strong>Description</strong> <br /> distribution managers need size column on the over under report</p> <p><strong>Recommended</strong> <br /> add size column next to item description on over under report</p> <p><strong>Mission Critical</strong> <br /> critical. otherwise personnel will have to pull a stock number listing and match up items to tell what they are looking at.</p> <p><strong>Benefits</strong> <br /> reduced errors and manpower savings.</p> <p><strong>Users</strong> <br /> all AFERMS</p>
20365warehouse transfer log tools01502WarehouseAF: AFERMSNewSubmitted: 06 Jun 2019<p><strong>Description</strong> <br /> WE can print an 1149 from the warehouse transfer screen, but air force TMOs will not accept an 1149 unless it is generated from the logistics tool suite at <a href="https://lts.wpafb.af.mil/">https://lts.wpafb.af.mil/</a>. </p> <p><strong>Recommended</strong> <br /> make DPAS talk to this system</p> <p><strong>Mission Critical</strong> <br /> time saver</p> <p><strong>Benefits</strong> <br /> eliminates double documentation</p> <p><strong>Users</strong> <br /> all AF</p>
20364UIC description01501WarehouseAF: AFERMSDoneSubmitted: 06 Jun 2019<p><strong>Description</strong> <br /> Our personnel know what units they are assigned to but the UIC means nothing to most members and is not recognizable. </p> <p><strong>Recommended</strong> <br /> everywhere there is an instance of UIC, add a "UIC description".  This includes UIC search blocks. there should be a UIC description option for searching.</p> <p><strong>Mission Critical</strong> <br /> critical.</p> <p><strong>Benefits</strong> <br /> personnel can use a recognizable format.</p> <p><strong>Users</strong> <br /> all</p> <p><strong>Completed – Release 2020.1 – 6 March 2020</strong></p>
20363TMO warehouse transfer01500WarehouseAF: AFERMSNewSubmitted: 06 Jun 2019<p><strong>Description</strong> <br /> We use TMO and hand carried warehouse transfers. sometimes hand carried transfers change.</p> <p><strong>Recommended</strong> <br /> give us a drop box on warehouse transfers that defaults to "TMO" and has an option of "non-TMO" shipment. If the shipment is TMO, then generate the 1149, if it is not then do not generate an 1149 and allow it to be canceled even after the ship button has been clicked as long as it hasn't been received on the gaining end.</p> <p><strong>Mission Critical</strong> <br /> important</p> <p><strong>Benefits</strong> <br /> erroneous jobs won't be generated after DPAS is tied into the TMO logtools system.</p> <p><strong>Users</strong> <br /> all AF</p>
20362stock items size column01499WarehouseAF: AFERMSNewSubmitted: 06 Jun 2019<p><strong>Description</strong> <br /> there is no size column on the stock items grid</p> <p><strong>Recommended</strong> <br /> add size column on stock items grid</p> <p><strong>Mission Critical</strong> <br /> highly important. I need to pull a stock number listing to compare stock numbers to sizes</p> <p><strong>Benefits</strong> <br /> manpower savings</p> <p><strong>Users</strong> <br /> all</p>
20361shipment reference number01498WarehouseAF: AFERMSNewSubmitted: 06 Jun 2019<p><strong>Description</strong> <br /> Once a warehouse transfer is shipped you can't do anything with it. We put the item in shipped status when we take it to TMO (the traffic management office).  When they actually ship the item they will send us a tracking number from the shipping company.  We should be able to adjust the shipment reference number after it is shipped to put the actual tracking number. for instance USPS, FedEx, UPS tracking numbers</p> <p><strong>Recommended</strong> <br /> make the shipment reference number editable after shipment.</p> <p><strong>Mission Critical</strong> <br /> important to maintain shipment visibility</p> <p><strong>Benefits</strong> <br /> shipment accountability</p> <p><strong>Users</strong> <br /> all</p>
20360DLA disposition01497WarehouseAF: AFERMSNewSubmitted: 06 Jun 2019<p><strong>Description</strong> <br /> we can dispose of items and generate 1348s in DPAS, but DLA makes us use the ETID system for turn in 1348s</p> <p><strong>Recommended</strong> <br /> tie DPAS into the DLADS and DARD ETID system.  create two new disposition options of "DLADS" and "DARD".</p> <p><strong>Mission Critical</strong> <br /> highly important</p> <p><strong>Benefits</strong> <br /> reduction of redundant data and access to systems.</p> <p><strong>Users</strong> <br /> all AFERMS</p>
20359delinquent warehouse transfer01496WarehouseAF: AFERMSDoneSubmitted: 06 Jun 2019<p><strong>Description</strong> <br /> We have warehouse transfers that sit in receiving in warehouses and the personnel don't receive them.</p> <p><strong>Recommended</strong> <br /> email personnel in the warehouses daily once the transfer has gone past its estimated delivery date by a week</p> <p><strong>Mission Critical</strong> <br /> highly important.  it throws off inventory numbers and shows the equipment as still being in the losing warehouse.</p> <p><strong>Benefits</strong> <br /> accurate inventory reporting.</p> <p><strong>Users</strong> <br /> all</p> <p><strong>Completed – Release 7.2.00 – 8 November 2019</strong></p>
20358component update on insp of issued items01495WarehouseAF: AFERMSNewSubmitted: 06 Jun 2019<p><strong>Description</strong> <br /> We can inspect an item that is issued, but cannot use serial update to change components. we understand the need to lock serialized components that a member signs for but we should be able to swap bulk components and print DW-01.</p> <p><strong>Recommended</strong> <br /> allow update of bulk components on issued items and print DW-01.</p> <p><strong>Mission Critical</strong> <br /> important</p> <p><strong>Benefits</strong> <br /> time savings. currently we would have to sign the item in and ensure we located the member and had them sign for it again before they flew.</p> <p><strong>Users</strong> <br /> All AFERMS</p>
20357JACKS update email notifications01494WarehouseAF: AFERMSNewSubmitted: 06 Jun 2019<p><strong>Description</strong> <br /> when Jacks makes changes to expiration dates there is no notification</p> <p><strong>Recommended</strong> <br /> send AFERMS users an email listing the NSNs, Lots, DOMs, old DOEs, and the new DOEs when JACKS does an update to AFERMS. We recommend using messaging subscriptions and Defaulting JACKS to AFERMS users</p> <p><strong>Mission Critical</strong> <br /> important</p> <p><strong>Benefits</strong> <br /> we will be know we have to go look at kits if there is a failure.</p> <p><strong>Users</strong> <br /> all AFERMS</p>
20356inventory update manager quantity edit01493WarehouseAF: AFERMSNewSubmitted: 06 Jun 2019<p><strong>Description</strong> <br /> when performing a Qty adjustment in inventory update mgr the old qty does not display which leaves room for error. if I have to reduce it by 1 and don't remember what it was I screw it up.</p> <p><strong>Recommended</strong> <br /> display the old qty column next to the selected NSNs and a new qty column that is adjustable next to them. See screen shot below</p> <p><strong>Mission Critical</strong> <br /> highly important</p> <p><strong>Benefits</strong> <br /> less errors on qty adjustments</p> <p><strong>Users</strong> <br /> ALL</p>
20355expiring items report include next insp in algorithm01492WarehouseAF: AFERMSDoneSubmitted: 06 Jun 2019<p><strong>Description</strong> <br /> The expiring items report does not account for items that will be pulled from service before their expiration date because they will not meet the inspection cycle</p> <p><strong>Recommended</strong> <br /> adjust the algorithm to include the next inspection of the parent SKO for the current fiscal year on time expiring components that are installed in that SKO.</p> <p><strong>Mission Critical</strong> <br /> highly important</p> <p><strong>Benefits</strong> <br /> currently the forecast is off and leads to emergency issue of munitions</p> <p><strong>Users</strong> <br /> all  </p> <p><strong>Completed – Release 2020.2.2 – 31 July 2020</strong></p>
20354Warehouse Manager role01491WarehouseAF: AFERMSNewSubmitted: 06 Jun 2019<p><strong>Description</strong> <br /> personnel that are already in system PCS to new warehouses and require roles requests to gain access to the new warehouse. Only warehouse officers can add cost centers. Personnel need temporary warehouse access for deployments.</p> <p><strong>Recommended</strong> <br /> create warehouse manager role  with the following abilities in addition to all technician abilities:</p> <ol> <li>grant a technician, who already has access in the AFERMS system, access to their specific warehouse.</li> <li>remove technician access to their warehouse</li> <li>assign an expiration date to warehouse access (for deployment purposes) <br /> we suggest using the warehouse, personnel assignment function for this.</li> <li>in conjunction with SCR warehouse kit options, set warehouse level kit options</li> <li>in conjunction with SCR inspection grouping, set warehouse level kit options</li> </ol> <p><strong>Mission Critical</strong> <br /> critical</p> <p><strong>Benefits</strong> <br /> operational capability in a deployed environment is greatly improved. data integrity in warehouses is improved.</p> <p><strong>Users</strong> <br /> all AFERMS</p>
20353Warehouse Kit Options01490WarehouseAF: AFERMSNewSubmitted: 06 Jun 2019<p><strong>Description</strong> <br /> Kits deploying to different AORs have different specific requirements for the environment.  warehouses have airframe and geographic location specific requirements for their locations.  It is extremely confusing having a large amount of optional components that always result in an "A" coded kit even if something mandatory at your location, but not marked as mandatory is missing .</p> <p><strong>Recommended</strong> <br /> allow warehouse manager role to:</p> <ul> <li>create local kit templates based off the LP kit. <br /> all components at LP would be mandatory, and they could make optional components mandatory as well as adjust the quantity.</li> <li>additionally, they should be able to make multiple kit recipe cards based off the specific location they are in(not location type, but specific warehouse location).</li> </ul> <p><strong>Mission Critical</strong> <br /> critical. currently kit integrity relies solely on human error because there are so many optional components.</p> <p><strong>Benefits</strong> <br /> data integrity, kit integrity</p> <p><strong>Users</strong> <br /> all AFERMS</p>
20352Inspection Grouping01489WarehouseAF: AFERMSNewSubmitted: 06 Jun 2019<p><strong>Description</strong> <br /> We have multiple kits of the exact same thing with different inspection cycles because of mission requirements.</p> <p><strong>Recommended</strong> <br /> allow warehouse officers to assign inspections to inspection sets at the NSN level.  Allow warehouse managers to select which inspection from the sets will be used in the warehouse.</p> <p><strong>Mission Critical</strong> <br /> highly important</p> <p><strong>Benefits</strong> <br /> reduced redundant kit creation. more adaptability to ins cycle changes when mission dictates</p> <p><strong>Users</strong> <br /> all AFERMS</p>
20351print ops01488WarehouseAF: AFERMSDoneSubmitted: 05 Jun 2019<p><strong>Description</strong> <br /> When printing the AF46 from the locations we print sign and scan the document back in.</p> <p><strong>Recommended</strong> <br /> add check box for electronic CAC/sig pad signature option when generating the 46. similar to the function in issue</p> <p><strong>Mission Critical</strong> <br /> important</p> <p><strong>Benefits</strong> <br /> time savings</p> <p><strong>Users</strong> <br /> all AFERMS</p> <p><strong>Completed – Release 7.2.00 – 8 November 2019</strong></p>
20350attachment method01487WarehouseAF: AFERMSDoneSubmitted: 05 Jun 2019<p><strong>Description</strong> <br /> Even though we aren't editing a location, we have to click edit to get to the attachment function. </p> <p><strong>Recommended</strong> <br /> use the print checkbox to select the item and have an attachment button on the main location grid.  See additional 3rd page below signature</p> <p><strong>Mission Critical</strong> <br /> important</p> <p><strong>Benefits</strong> <br /> time savings, prevent someone accidentally editing a location</p> <p><strong>Users</strong> <br /> all AFERMS</p> <p><strong>Completed – Release 7.2.00 – 8 November 2019</strong></p>
20349DW01 available for non-kitted items with inspections01486WarehouseAF: AFERMSDoneSubmitted: AF: AFERMS<p><strong>Description</strong> <br /> We have some equipment loaded as stand alone items not kitted.  these items have multiple inspections slated against them. we have no means of viewing which inspection is due on the item because there is no DW01 available for the item</p> <p><strong>Recommended</strong> <br /> allow a DW01 to be printed for an item that is not a kit, but has inspections against it.</p> <p><strong>Mission Critical</strong> <br /> critical</p> <p><strong>Benefits</strong> <br /> availability to view inspection data</p> <p><strong>Users</strong> <br /> all</p> <p><strong>Completed – Release 7.2.00 – 8 November 2019</strong></p>
20348Repair Parts Grid01485WarehouseAF: AFERMSDoneSubmitted: 05 Jun 2019<p><strong>Description</strong> <br /> the repair parts grid is not user friendly, it doesn't pull a part automatically from a location. Checking the box then hitting a edit button and then adjusting quantity is to many clicks.</p> <p><strong>Recommended</strong> <br /> add a location column with a drop menu of locations that have the part in stock to choose where to pull the part from. <br /> In addition, the required quantity should default to the repairable quantity and remain adjustable.<br />allow a default location for repair parts to be set at the stock item.</p> <p><strong>Mission Critical</strong> <br /> highly important</p> <p><strong>Benefits</strong> <br /> time saving. we will use the system to track all our expendable supplies and it will encompass all our stock. allowing for clearer budgeting</p> <p><strong>Users</strong> <br /> all</p> <p><strong>Completed – Release 2020.1 – 6 March 2020</strong></p>
20347QC Select Items01484WarehouseAF: AFERMSDoneSubmitted: 05 Jun 2019<p><strong>Description</strong> <br /> When I use the select items function in the QC edit grid, it gives me the option to select any item that is the same NSN. It does not limit this selection to the items that were on the original inspection.</p> <p><strong>Recommended</strong> <br /> filter the list so that only items on the original inspection can be selected.</p> <p><strong>Mission Critical</strong> <br /> highly important</p> <p><strong>Benefits</strong> <br /> prevent data errors.</p> <p><strong>Users</strong> <br /> all AFERMS</p> <p><strong>Completed – Release 7.2.00 – 8 November 2019</strong></p>
20346Lost In Transit01483WarehouseAF: AFERMSNewSubmitted: 05 Jun 2019<p><strong>Description</strong> <br /> If a warehouse transfer is lost in transit, say for instance the aircraft it was on crashed, and the gaining unit then refuses receipt, the gear goes back into the losing warehouse.  </p> <p><strong>Recommended</strong> <br /> give us an option on receiving of "lost in transit". This would close the job and dispose of the items instead of putting them back in the losing warehouse. </p> <p><strong>Mission Critical</strong> <br /> important. saves the trouble of figuring out why you have a bunch of equipment you shipped out showing up in your warehouse, then trying make sure you dispose of the right ones.</p> <p><strong>Benefits</strong> <br /> accuracy of inventory is enhanced.</p> <p><strong>Users</strong> <br /> all</p>
20345Inventory Count Components01482WarehouseAF: AFERMSNewSubmitted: 5 Jun 19<p><strong>Description</strong> <br /> the inventory function only counts stock and does not count kit components.  this does not help me when I am trying to count accountable items. If I have to do a hand count for an R14 inventory, I will have to count items in kits as well.</p> <p><strong>Recommended</strong> <br /> add check box to include components, in similar fashion to ICN inquiries. in addition it should have a parent serial number column.</p> <p><strong>Mission Critical</strong> <br /> highly important. the inventory function is of no use to us until this is resolved.</p> <p><strong>Benefits</strong> <br /> accurate inventory</p> <p><strong>Users</strong> <br /> all AFERMS</p>
20344AUIC PA Lookup01481PAAF: GEITNewSubmitted: 22 May 2019<p><strong>Description</strong> <br /> DPAS does not have an inquiry for looking up the Property Administrator tied to an AUIC.  Recommend creating an inquiry for AUIC Property Administrator lookup that can be utilized by Property Administrators across the FF-GEIT site.  </p> <p><strong>Recommended</strong> <br /> Recommend creating an inquiry that will allow lookup of Property Administrators tied to AUICs.  Need to be able to find name, email and phone number.</p> <p><strong>Mission Critical</strong> <br /> Yes.  When we as the IO or other Property Administrators are trying to find points of contact at the AUIC level, we cannot.  This is crucial for communication when working with each other to process transactions.</p> <p><strong>Benefits</strong> <br /> Main benefit would be the ability to find and contact an AUIC's Property Administrator quickly.  IO and Property Administrators need this to reduce time for looking up contact information.  Contact information will assist IOs with keeping track of who the Property Administrators are and will assist Property Administrators when researching asset history and performing transfer transactions within DPAS.</p> <p><strong>Users</strong> <br /> Yes, all IOs and Property Administrators have the need to obtain this information quickly and do not have an option for this function at this time.</p>
20343Individual Sales Analyst Role01480WarehouseAF: USAFADoneSubmitted: 05/29/2019<p><strong>Description</strong> <br /> USAFA is generating a report to pass off to local finance management. The current process is to email this report to the finance department. USAFA requires a role to grant the finance office access to the Member Sales Report from DPAS.</p> <p><strong>Recommended</strong> <br /> Create a role that grants read only access to the Individual Sales Report in DPAS Warehouse. Financial Management cannot have access to any other information in DPAS.</p> <p><strong>Mission Critical</strong> <br /> Mission Critical. Emailing this information is a security risk. A more secure solution will be to have finance log into DPAS to download this monthly report.</p> <p><strong>Benefits</strong> <br /> Improves Accuracy, Accountability, Security, and provides financial reporting to the finance office directly.</p> <p><strong>Users</strong> <br /> Only USAFA users; however, anyone could use it.</p> <p><strong>Completed – Release 7.1.2 – 30 Aug 2019</strong></p>
20342Indiv. Issue/Return Technician01479WarehouseAF: USAFADoneSubmitted: 05/29/2019<p><strong>Description</strong> <br /> USAFA Hires interns to cover major issue and return days. A role that limits access to only the individual issue and return processes is requires to streamline training and provide only the access that these temporary workers require.</p> <p><strong>Recommended</strong> <br /> Create a role with subsequent training that gives access only to the Individual Issue and Return processes in the Warehouse Module.</p> <p><strong>Mission Critical</strong> <br /> Mission Critical. USAFA cannot spend the time and money training interns on processes they are not allowed to use. USAFA cannot take the security risk for interns to have access to more than just the issue and return processes.</p> <p><strong>Benefits</strong> <br /> Reduces time and cost of training. Increases information security.</p> <p><strong>Users</strong> <br /> All DPAS users</p> <p><strong>Completed – Release 7.1.2 – 30 Aug 2019</strong></p>
20341Report Calculations01478MUOSDNewSubmitted: 23 May 2019<p><strong>Description</strong> <br /> In reporting module, unable to do calculations such as sum, averages, etc., to show on report.</p> <p><strong>Recommended</strong> <br /> Provide the ability to perform calculations such as sum, averages, etc., in the system for reports.</p> <p><strong>Mission Critical</strong> <br /> Yes.  Non Tactical Vehicle average mileage is used to measure against DoD minimum mileage goals for the Vehicle Utilization Review Board (VURB)</p> <p><strong>Benefits</strong> <br /> Supports the installation commander's policy to base vehicle retention on average monthly mileage goals as the first criteria.</p> <p><strong>Users</strong> <br /> Yes</p>
20340Physical Inv Location Added01477WarehouseUSMC: CSPNewSubmitted: 5/22/2019<p><strong>Description</strong> <br /> Currently the location is not visible in the Physical Inventory Reconciliation summary is is only visible in the Physical Inventory reconciliation details.   </p> <p><strong>Recommended</strong> <br /> Recommend that the location be added to the Physical Inventory Reconciliation Summary page. </p> <p><strong>Mission Critical</strong> <br /> Yes this will help keep accurate physical inventory records by location.  This would also help during inspections when we are required to report what locations have been inventoried in a month.</p> <p><strong>Benefits</strong> <br /> Having this functionality will help warehouses keep accurate Physical Inventory accountability by location.  Which will improve the accuracy of reporting from the warehouse level.</p> <p><strong>Users</strong> <br /> All IIF/UIF</p>
20339Lock/Freeze Locations01476WarehouseUSMC: CSPRemovedSubmitted: 20 May 2019<p><strong>Description</strong> <br /> Currently in the DPAS-WM there is a Freeze Location Check Box when you edit or add a location.  Currently checking this box is not doing anything, we are still able to move items in and out of the location.  Also there is no ability to Freeze a location during Physical Inventory of a location.     </p> <p><strong>Recommended</strong> <br /> Recommend that the when the freeze locations check box is checked that no items are allowed to be moved in or out of this location.  I would also like to recommend that when doing a Physical Inventory of a location that the location will be locked down no items will be allowed into or out of that location until the physical inventory of that location has been fully reconciled.     </p> <p><strong>Mission Critical</strong> <br /> Yes this will help keep accurate inventory during the inventory process and also help us with our Quarantine Items that is mandated by Headquarters Marine Corps and Syscom to be stored in a Locked or frozen location so nothing can be taken out or put into this Quarantine location.</p> <p><strong>Benefits</strong> <br /> Having this functionality will help warehouses keep accurate Inventory accountability.  Which will improve the accuracy of reporting from the warehouse level.</p> <p><strong>Users</strong> <br /> All IIF/UIF</p> <p><strong>28 May 2019 – cancelled per Jim Grimes </strong> <br /> Duplicate of <a href="index.php/support/system-change-request/details/4/20039/lock-freeze-locations">SCR #01212</a>.</p>
20338Label field selection update01475PAAF: GEITNewSubmitted: 17 May 2019<p><strong>Description</strong> <br /> The DPAS Label field selection does not allow for the mandatory fields needed for AF IT equipment. See attached screen shot.<br />Propose adding the fields needed to the selection table: Part #, Model #, Cage Code.</p> <p><strong>Recommended</strong> <br /> Recommend adding the following fields needed to the selection table: <br />Part #, Model #, Cage Code</p> <p><strong>Mission Critical</strong> <br /> Yes.  Without the fields listed above, Property Administrators cannot create labels that will meet AF Mandated criteria for labeling IT assets.</p> <p><strong>Benefits</strong> <br /> Enables PAs to properly label their IT assets and meet AF standards for labeling.</p> <p><strong>Users</strong> <br /> Yes, all users within FF-GEIT will require these fields when creating labels. </p>
20337Authorization Flow01474WarehouseAF: OtherNewSubmitted: 17 May 2019<p><strong>Description</strong> <br /> Provide process in DPAS for AF GFM-A Program Offices to record their authorization for their CICPs to adjust inventory, dispose an asset or condemn an asset. </p> <p><strong>Recommended</strong> <br /> AF CICPs contact the AF GFM-A Program Offices with their requests to adjust inventory, dispose of an asset or condemn an asset. </p> <ol> <li>The Program Office reps records the request in DPAS</li> <li>DPAS provides an authorization number</li> <li>the CICP enters the authorization number in the application DLMS transaction</li> <li>DPAS receives the DLMS transaction and matches with the pre-approved list</li> <li>If no match is found, DPAS sends a notification to the AF GFM-A Program Office</li> </ol> <p>See attached for process flow chart, contextual model narrative and IT functional requirements (ITFRs).</p> <p><strong>Mission Critical</strong> <br /> This is mission critical.  This allows the AF Program Managers to review and approve requests before they occur.</p> <p><strong>Benefits</strong> <br /> This authorization process does not currently exist in DPAS and implementation of this solution will meet the GFM-A needs which will focus on FIAR compliance.</p> <p><strong>Users</strong> <br /> ALL AF GFM-A users</p>
20336Master Vehicle Report (MVR)01473PAAF: VSCOSNewSubmitted: 15 May 2019<p><strong>Description</strong> <br /> Need a report to view Authorization details and the assets assigned. Create an Inquiry in the APO module.</p> <p><strong>Recommended</strong> <br /> Build an inquiry in the APO module for users to generate a Master Vehicle Report (MVR) Inquiry.  Report needs to be accessible to users at the UIC and enterprise level.  Please see attached sample and reference help ticket 5795.</p> <p><strong>Mission Critical</strong> <br /> Yes, Vehicle Fleet Managers require this to effectively manage their fleets.  They need the ability to see Authorization Details and the assets assigned to those details by UIC, a MAJCOM, a specific user and Authorization type.</p> <p><strong>Benefits</strong> <br /> This will streamline and consolidate multiple reports currently required to see Authorization Details and the assets assigned to those details by UIC, a MAJCOM, a specific user and Authorization type.</p> <p><strong>Users</strong> <br /> Yes.  This change will affect all Vehicle Management units across the Air Force an may also benefit other services/agencies.</p>
20335Physical Inventory History Inquiry01472WarehouseLeidosNewSubmitted: 15 May 2019<p><strong>Description</strong> <br /> Right now, the only way to pull a list of completed Physical Inventories is to go to each Warehouse and do it one by one on each Warehouse. This is not very feasible for our users to have to go to each warehouse. We will need to develop a history inquiry that users can search on Physical Inventories as needed. <br /> Request from NSWC: <br />Can you guys pull a listing of all the 'CRC - Closed - Reconciled' Physical Inventories for LP's NSWC WH and NSWC WH Armory. Since there is no way for us to do this as the end user LP wide, Justin suggested we submit a ticket to make this happen. <br /> We will need the following fields for this data pull:</p> <ul> <li>Condition Cd(s)</li> <li>Cost Center</li> <li>Established By</li> <li>Established Dt/Tm</li> <li>Expected Completion Dt</li> <li>Facility/Facilities</li> <li>ICP Physical Inv Nbr</li> <li>Interface System Cd</li> <li>Inv Execution Type</li> <li>Inv Release Type</li> <li>Inv Segment Cd</li> <li>Inv Type</li> <li>Last Transaction Dt/Tm</li> <li>Last Updated By</li> <li>Location</li> <li>Logistics Program</li> <li>Owning DoDAAC</li> <li>Personnel</li> <li>Physical Inv Nbr</li> <li>Physical Inv Status</li> <li>Prj Cd</li> <li>Program Id</li> <li>Region</li> <li>Reportable Commodity Type(s)</li> <li>Request Type</li> <li>Scheduled Start Dt</li> <li>Sequence Nbr</li> <li>Serial Nbr(s)</li> <li>Serial Number(s)</li> <li>Site</li> <li>Stock Nbr(s)</li> <li>Warehouse</li> <li>Zone(s)</li> </ul> <p><strong>Recommended</strong> <br /> Create an inquiry or report that allows a user the ability to pull the history of all completed physical inventories.</p> <p><strong>Mission Critical</strong> <br /> N/A</p> <p><strong>Benefits</strong> <br /> Reduces wait time for the user to get their data.</p> <p><strong>Users</strong> <br /> All</p>
20334Master data Location RPUID search field add01471PANavyNewSubmitted: 10May2019<p><strong>Description</strong> <br /> Encountered numerous complications with the limited search fields in the Master data > Location > RPUID screen. Results on the query exceed the 500 returned lines. Additional filters are necessary to limit return results.</p> <p><strong>Recommended</strong> <br /> Request to add the following search fields to the MASTER DATA > LOCATION > RPUID search window:</p> <ul> <li>Facility Number</li> <li>Installation Number</li> </ul> <p><strong>Mission Critical</strong> <br /> This change will help identify an RPUID quicker by the APO.</p> <p><strong>Benefits</strong> <br /> Reduction in man hours conducting searches for RPUID numbers, streamlined data results, and more effective search methods</p> <p><strong>Users</strong> <br /> All users</p>
20333UNIT SCHEDULING CAPABILITY01470WarehouseUSMC: CSPDoneSubmitted: 1 MAY 2019<p><strong>Description</strong> <br /> Currently there is no capability for Units to schedule an appointment with a Unit Issue Facility for Unit Issues, Returns or Exchanges.</p> <p><strong>Recommended</strong> <br /> Recommend that Units have the capability to log in and schedule appointments for Unit Issues, Returns and Exchanges.</p> <ol> <li>  Ability to choose type of Service i.e., Unit Issue, Return or Exchange.</li> <li>  Ability to pick time of Appointment.</li> </ol> <p><strong>Mission Critical</strong> <br /> Yes. Deputy Chief of Staff, Installations and Logistics has tasked the CSP with conducting a Proof of Principle in order to examine new ways of operating in order to reduce customer wait time.  Unit Issue/Return capability will reduce customer wait time, help spread-load the daily workload, and help the 3PL support provider to better plan and maximize use of human resources. </p> <p><strong>Benefits</strong> <br /> Having Unit Issue/Return scheduling capability will reduce customer wait time, help spread-load the daily workload, and help the 3PL support provider to better plan and maximize use of human resources. It will also set the stage for use of autonomous robotics, as well as delivery. </p> <p><strong>Users</strong> <br /> All UIF customers.</p> <p><strong>Completed – Release 2021.1 – 5 February 2021</strong></p>
20332Appointment AUD Access01469WarehouseUSMC: CSPDoneSubmitted: 30 Apr 2019<p><strong>Description</strong> <br /> Currently the below roles do not have Read Only access to the Appointment AUD Access So they are unable to view if the warehouse has any scheduled appointments.  Thus making it extremely difficult for the warehouse to know if they have any appointments coming up unless a Manager is on site.</p> <ul> <li>CSP STAKEHOLDER</li> <li>SITE MANAGER</li> <li>FACILITY CLERK</li> <li>SUPPLY TECH</li> <li>LINE CLERK</li> </ul> <p><strong>Recommended</strong> <br /> Recommend that the below roles be given Read Only access to the Appointment AUD</p> <ul> <li>CSP STAKEHOLDER</li> <li>SITE MANAGER</li> <li>FACILITY CLERK</li> <li>SUPPLY TECH</li> <li>LINE CLERK</li> </ul> <p><strong>Mission Critical</strong> <br /> Yes, This will help us the warehouse to be able to identify when appointments will be coming into the warehouse.  Currently a Manager needs to be at the warehouse to see the appointments.  This is not always the case in our warehouse operations.</p> <p><strong>Benefits</strong> <br /> Having this functionality will be extremely helpful so the entire warehouse knows what appointments will be coming on any given day.</p> <p><strong>Users</strong> <br /> All IIF/UIF</p> <p><strong>Completed – Release 7.0.3 – 7 June 2019</strong></p>
20331Job Order Nbr Inquiry01468MUOSDNewSubmitted: 04/29/2019<p><strong>Description</strong> <br /> Current Job Order Nbr Inquiry does not reflect reimbursable transactions.  Would like to list all transactions against a Job Number like you see for mileage for Dispatches.  Also the 'Avail Dol Amt' does not produce a entry.</p> <p><strong>Recommended</strong> <br /> Add the following to the 'Field' List:  Dispatch ID, Total Base Cost, Total Utilization Cost and Total Dispatch Cost. There is no workaround since Dispatch Inquiry does not list any cost fields.</p> <p><strong>Mission Critical</strong> <br /> Mission critical to verify accuracy of reimbursable charges and ensure all transactions are captured.</p> <p><strong>Benefits</strong> <br /> Accuracy of cost and transactions captured.</p> <p><strong>Users</strong> <br />  </p>
20330Dispatch Inquiry Fields01467MUOSDNewSubmitted: 04/29/2019<p><strong>Description</strong> <br /> When doing a Dispatch Inquiry, it would be good to identify reimbursable Dispatches.</p> <p><strong>Recommended</strong> <br /> Add the following to the 'Field' List:  Dispatch Desc, Total Base Cost, Total Utilization Cost and Total Dispatch Cost</p> <p><strong>Mission Critical</strong> <br /> Critical to Reimbursable users to track cost</p> <p><strong>Benefits</strong> <br /> Financial and mission accuracy for reimbursable transactions.</p> <p><strong>Users</strong> </p>
20329Dispatch Job Order Update01466MUOSDNewSubmitted: 04/29/2019<p><strong>Description</strong> <br /> A closed Dispatch cannot add/update Job Order Nbr.  Job Order Number Browser opens but will not allow you to select a Job Order Nbr. </p> <p><strong>Recommended</strong> <br /> Either allow a closed Dispatch to be updated to assign a Job Order Nbr and capture reimbursable cost or reopen a dispatch to make corrections and then close. </p> <p><strong>Mission Critical</strong> <br /> Critical to capture all reimbursable transactions that may not have been identified as reimbursable at time of Issue or Closure.</p> <p><strong>Benefits</strong> <br /> Accurate tracking to reimbursable cost when using DPAS solely as the cost generator.</p> <p><strong>Users</strong> <br /> Only those considered Resource Managers who control Fleet Budget.</p>
20328Dispatch Mileage Flag00628MUOSDDoneSubmitted: 03/11/2014<p><strong>Description</strong> <br /> DPAS to flag any dispatch exceeding 1000 miles. ADDED Each Agency has a mileage limit per dispatch in their policy.  To assist capture violators, DPAS will be able to exploit the utilization captured to alert leadership.  I also believe having this as a Master Data function, will allow the Agencies to set their own separate mileage limits.</p> <p><strong>Recommended</strong> <br /> Either allow distance to be set under Master Data by user or set flag to show when total dispatch is 1000 or more miles.  Just flag in red above tabs.  Flag during Dispatch Return and on the Maintenance Action List would help</p> <p><strong>Mission Critical</strong> <br /> Critical to agency and component level regulations</p> <p><strong>Benefits</strong> <br /> Reduces time and improves accuracy of utilization.</p> <p><strong>Users</strong></p> <p>Combined with SCR #<a href="index.php/support/system-change-request/details/4/20041/utilization-fuel-variance-report-s">01214</a></p> <p><strong>Completed – Release 7.0 – 20 April 2019</strong></p>
20327Open Warehouse Actions and ICN Inventory Update01465WarehouseAF: VSCOSNewSubmitted: 25 April 2019<p><strong>Description</strong> <br /> Materiel Control technicians need to be aware of all open items that require their attention. Currently, not all Inspection Types display as Open Warehouse Actions on the Message of the Day dashboard. Also, the ICN Inventory inquiry does not display previous and upcoming inspection dates for all Inspection Types.</p> <p><strong>Recommended</strong> <br /> Currently, the DPAS Warehouse only displays upcoming and open inspections with a "INSPECTION" action code. This capability needs to be extend to the rest of the Inspection Actions (cannibalization, inspections, Quality Control, Maintenance, Test, Calibration, Other, Assessment). Additionally, Warehouse Inventory Inquiries only display date information for "Inspection", "Test", "Calibration", and "Maintenance" Inspection Actions. This feature also needs to be implemented for the rest of the Inspection Actions.</p> <p><strong>Mission Critical</strong> <br /> AFI 24-302, 5.41.2.6. Materiel Control ensures Test, Measurement and Diagnostic Equipment (TMDE) tools are scheduled for calibration and certification according to TO 00-20-14-WA-1. Use a visual display board or computer-generated listing to keep the current status of all TMDE requiring calibration.</p> <p><strong>Benefits</strong> <br /> Displaying all items requiring user action under Message of the Day will allow better management of warehouse operations and prevent any overdue calibrations/tests. Inventory inquiries with all previous and upcoming inspections will help meet AFI requirement.</p> <p><strong>Users</strong> <br /> The entire Air Force component and other services will benefit from having better visibility of all items requiring user action and from having an inventory that displays inspection information for all Inspection Types.</p>
20326Replenishment & On-Hand Qty Inquiry01464WarehouseAF: VSCOSRemovedSubmitted: 25 April 2019<p><strong>Description</strong> <br /> The DPAS Warehouse Module does not have an inquiry that displays on-hand quantities and includes replenishment parameters. A listing with this information is necessary to monitor stock levels.</p> <p><strong>Recommended</strong> <br /> Recommend adding inquiry that displays ICN inventory data for assets with replenishment parameters or add option to filter the ICN Inventory inquiry to replenishment items only. This new or upgraded inquiry needs to display replenishment parameters & inventory information.</p> <p><strong>Mission Critical</strong> <br /> AFI 24-302 mandates Materiel Control to monitor stock items to ensure correct prices are maintained and to adjust replenishment parameters based on demand. Materiel Control also needs to monitor shelf-life data to replenish expiring stock items.</p> <p><strong>Benefits</strong> <br /> The ability to monitor stock levels for replenishment items will ensure availability of essential items reducing vehicle downtime.</p> <p><strong>Users</strong> <br /> The entire Air Force component as well as other services will benefit from having the ability to analyze and compare on-hand quantities against replenishment parameters.</p> <p><strong>24 Jun 2019 – cancelled per Anthony Sledge </strong> <br /> As additional capabilities have already been added since we submitted this SCR earlier.</p>
20325Enterprise Mass Upload Capability01463EnterpriseAF: VSCOSNewSubmitted: 25 April 2019<p><strong>Description</strong> <br /> Air Force VM users are required to add new part numbers (Stock Numbers) to the catalog on a daily basis due to the diversity of our vehicle fleet. This loading process can be very tedious and time consuming for the end user.</p> <p><strong>Recommended</strong> <br /> We recommend creating a role for enterprise level entities and give them the capability to  mass upload Stock Numbers/Stock Items. Personnel with this access will receive requests from lower level users and validate/manage upload requests entered into the system.</p> <p><strong>Mission Critical</strong> <br /> AFI 24-302 mandates the 441 VSCOS to streamline the data upload process, request engineering assistance to resolve technical constraints, engineer products and, technical processes needed for management of vehicles.</p> <p><strong>Benefits</strong> <br /> This capability will save countless end user man-hours along with improving data accuracy.</p> <p><strong>Users</strong> <br /> The entire Air Force component, as well as other services, will benefit from having this mass upload capabilities.</p>
20324Asset Inventory Reports01462PAAF: AFERMSNewSubmitted: 23 April 2019<p><strong>Description</strong> <br /> Asset records in "pending transfer" show up on both losing and gaining custodian inventory reports</p> <p><strong>Recommended</strong> <br /> Remove assets pending transfer from inventory reports, however, ensure assets pending approval are retained.  Create a separate report to identify assets pending transfer.</p> <p><strong>Mission Critical</strong> <br /> This is mission critical due to custodians refusing to sign inventories for assets they're no longer in possession of.</p> <p><strong>Benefits</strong> <br /> Improves accountability</p> <p><strong>Users</strong> <br /> yes</p>
20323Asset Inquiry Selection Addition01461PAAF: OtherNewSubmitted: 22 Apr 2019<p><strong>Description</strong> <br /> To generate reports necessary for FIAR reporting and general inquiries the CAGE cd, Installation Code (Instl Cd) and Major Command (Major Cmd Cd) are needed in the Asset Inquiry selection table.</p> <p><strong>Recommended</strong> <br /> Add CAGE cd, Installation Code (Instl Cd) and Major Command (Major Cmd Cd) to the Asset Inquiry selection table.</p> <p><strong>Mission Critical</strong> <br /> Yes.  As Air Force Equipment Control Officers, these fields are needed when building, grouping, and sorting reports.</p> <p><strong>Benefits</strong> <br /> Enables users to create reports tailored to certain functions of AF IT Asset Management.</p> <p><strong>Users</strong> <br /> Yes, all users within FF-GEIT will require these fields when performing asset inquiries.  they are available on other inquiry screens, but not this one.</p>
20322AFWay Interface01460PAAF: OtherDoneSubmitted: 17 Apr 2019<p><strong>Description</strong> <br /> AFWay and DPAS have an interface established to sync data for Equipment Custodian Numbers, DODAAC and UIC information.  The initial information DPAS is providing during the nightly sync does not include Custodian Numbers necessary for AFWay to support the Air Force Approval Process.  The original request was to have the DODAAC and UIC only provided through a nightly sync from DPAS and through testing AFWay identified the need for the Custodian Numbers.</p> <p><strong>Recommended</strong> <br /> Add Custodian Numbers field and the association to the DODAAC and UIC to the nightly sync.</p> <p><strong>Mission Critical</strong> <br /> Yes.  Mandatory Use policy AFMAN 12-1703 mandates Air Force purchase ALL IT products  through AFWay. </p> <p><strong>Benefits</strong> <br /> Enables AFWay compliance with AFMAN 12-1703, ensuring the continuation of Air Force approval processes.</p> <p><strong>Users</strong> <br /> This affects approximately 60K AFWay customers and will cause work stoppage of over 4,500 Air Force Request for Quotes and 1,800 Orders on average every quarter in AFWay.</p> <p><strong>Completed – Release 2020.1.2 – 17 April 2020</strong></p>
20321PA Inquiry Field Additions01458PADSSNewSubmitted: 4/11/19<p><strong>Description</strong> <br /> Currently when a query in PA for an asset management search under asset is missing the ability to query on the manufacturer name, model or part #.  But I have to pull down the entire inventory and then build these into my field and sort through the excel spreadsheet.</p> <p><strong>Recommended</strong> <br /> Add the ability to query by manufacturer name or model or part # under the query field.</p> <p><strong>Mission Critical</strong> <br /> no</p> <p><strong>Benefits</strong> <br /> reduces time</p> <p><strong>Users</strong> <br /> all users</p> <p><strong><span style="color: #1f497d; font-family: 'Calibri',sans-serif; font-size: 11pt;"> </span></strong></p>
20320AAR Decrease Terms Update01457PADSSNewSubmitted:4/11/19<p><strong>Description</strong> <br /> Currently when an asset ID that has been associated with a record that has been tagged and recorded in the IUD registry it gives a drop down of options that are not associated w/ an administrative adjustment.</p> <p><strong>Recommended</strong> <br /> Would suggest that possible options of an AAR decrease would also include "double posting", "error in posting" or/and "non-accountable"</p> <p><strong>Mission Critical</strong> <br /> Could be an audit discrepancy</p> <p><strong>Benefits</strong> <br /> improves accuracy</p> <p><strong>Users</strong> <br /> all users of IUID</p>
20319Implement Validation of Trading Partner Info01459PALeidosNewSubmitted: 4/15/2019<p><strong>Description</strong> <br /> DAI has requested that DPAS review its validation of Trading Partner (TP) data within its Accounting Transactions.  They are seeing some transactions that they believe should contain TP data, but do not.  Note:  They could be old transactions as their review encompassed a large time period. They are also receiving Accounting Transactions where the TP data is not valid.  They would like to see DPAS implement additional validation for TP data.  Currently DPAS is only validating the Department Cd allowing the user to type in the Main Account and Limit with only validation that it be 4 characters.</p> <p><strong>Recommended</strong> <br /> DPAS feeds several Accounting Systems that require TP2, TP4, and TP5 data.  DAI and SABRS are two notable interfaces, but there could be others as the DAI interface is considered the current std for new accounting interfaces.  It is recommended that DPAS establish master lookup tables for TP4 (Basic Symbol / Main Account) and TP5 (Subhead/Limit),in addition to the current Department Cd lookup and create associations between them.  The information to populate these lookup values is available from the DFAS Manual 7097.01, Treasury Website and/or from the DCMO Authoritative SFIS Values website. For Non-097 appropriation, the limit/subhead may not be required/applicable. It is also recommended that DPAS review the capture of TP data for all accounting systems regardless of whether that interface accepts the data. Even if the accounting interface does not support it, the user may be required to provide this information off-line.</p> <p><strong>Mission Critical</strong> <br /> Yes - As the DoD continues to strive for FIAR compliance, accurate reporting of PP&E financial activity is essential.</p> <p><strong>Benefits</strong> <br /> Improves financial reporting accuracy, and reduces the time required to input the data.</p> <p><strong>Users</strong> <br /> Yes</p>
20318PA Asset Activity History01456PADECANewSubmitted: 4/10/19<p><strong>Description</strong> <br /> When querying PA asset history, the most current transaction overwrites historical data and takes additional time to decipher the current data.  Also, shows the same record multiple times.</p> <p><strong>Recommended</strong> <br /> Show true asset transactions in date order to provide a cleaner tracking of asset history.</p> <p><strong>Mission Critical</strong> <br /> Mission Critical, to provide a more accurate detail history record per asset ID.</p> <p><strong>Benefits</strong> <br /> To provide a more accurate detail history record per asset ID and reduce time in finding record history.</p> <p><strong>Users</strong> <br /> This affects all PA users.  Need to provide a more accurate detail history record per asset ID.</p>
20317Print Dispatch Calendar01455MUOSDNewSubmitted: 01April2019<p><strong>Description</strong> <br /> Print Dispatch Calendar from M&U Dashboard.</p> <p><strong>Recommended</strong> <br /> Print Dispatch calendar as a .PDF from the Dashboard. Print day/week/month format.  Currently use Outlook calendar.</p> <p><strong>Mission Critical</strong> </p> <p><strong>Benefits</strong> <br /> Allows for a visual makeup of dispatch for non-DPAS users without dual efforts.</p> <p><strong>Users</strong> <br /> M&U users</p>
20316M&U AWD Updates01454MUOSDNewSubmitted: 01April2019<p><strong>Description</strong> <br /> Vehicle Disposition functional improvements</p> <p><strong>Recommended</strong></p> <ul> <li>When AWD is selected and FAST Disp Reason assigned in M&U, Asset Mgmt > Pending Transaction > Disposition > Turn-in/Disposal will have the record available for approval.</li> <li>AWD will not be available for assets with open Dispatch or Work Order.</li> </ul> <p><strong>Mission Critical</strong> <br /> Mission critical for accurate accountability</p> <p><strong>Benefits</strong> <br /> Improves accuracy of accountability</p> <p><strong>Users</strong> <br /> Fleet Mgrs and APO</p>
20315Member Mass Load01453MUOSDNewSubmitted: 01April2019<p><strong>Description</strong> <br /> Member information is required to populate the Operators and Technician fields in DPAS M&U.  Need a way to mass load other than during conversion.</p> <p><strong>Recommended</strong> <br /> As used in DPAS Warehouse>Member Profile, have the ability to import information from a DPAS template.  Also have the ability to delete profile.</p> <p><strong>Mission Critical</strong> <br /> Mandated for Dispatch and Work Order personnel identification.</p> <p><strong>Benefits</strong> <br /> Reduces time loading a user before Dispatch/WO.  Accuracy of identifying user from a DPAS table.</p> <p><strong>Users</strong> <br /> Operators of vehicles and technicians on Work Orders.</p>
20314GFM-A Account Manager New User Role01452WarehouseAir ForceDoneSubmitted: 27 Mar 2019<p><strong>Description</strong> <br /> AF GFM-A team has reviewed the current list of DPAS user roles and none of the current DPAS roles meet our requirements. </p> <p><strong>Recommended</strong> <br /> Request establishment of new user role for AF GFM-A Warehouse module users to meet AF GFM-A needs.  We recommend naming the new role - GFM-A Account Manager.  Also, training needs to be built to correspond to this new role.  See the attached DPAS User Role form for requested Pgm IDs for this role and training.</p> <p><strong>Mission Critical</strong> <br /> This is mission critical.  The new user role is necessary to enter transactions and the training is mandated to perform user role functions.</p> <p><strong>Benefits</strong> <br /> The desired role (GFM-A Account Manager) does not currently exist in DPAS and implementation of this solution will meet the GFM-A needs which will focus on GFM-A requirements training for users to be FIAR compliant.</p> <p><strong>Users</strong> <br /> ALL AF GFM-A users</p> <p><strong>Completed – Release 7.1 – 26 July 2019</strong></p>
20313Miles per Gallon on Report01451MUOSDNewSubmitted: 19 March 2019<p><strong>Description</strong> <br /> One of the FAST VLD Vehicle Type flags is Miles Per Gallon.  Would be a great check to have the MPG listed by the vehicle.</p> <p><strong>Recommended</strong> <br /> On the DPAS FAST Outbound Report, the Vehicle Tab has a blank 'Comment' column.  FAST does not pull information from this column.  Would like DPAS to post calculated MPG from DPAS FYTD data for miles and fuel.</p> <p><strong>Mission Critical</strong> <br /> Mission critical in data integrity to capturing erroneous entries monthly.</p> <p><strong>Benefits</strong> <br /> Improves accuracy of data reported to FAST.  Reduces time determining vehicles with Flagged data.</p> <p><strong>Users</strong> <br /> M&U Officer and M&U Dispatch Specialist for Fleet.</p>
20312OCONUS Fuel Quantity to Liters01450MUOSDNewSubmitted: 14 March 2019<p><strong>Description</strong> <br /> Fuel measurement OCONUS is in Liters but needs to be reported in FAST as Gallons. Need the ability to identify assets that use Liters.</p> <p><strong>Recommended</strong> <br /> As with Utilization Measure Code being changeable between Miles and Kilometers, Fuel Quantity needs to be as well between Gallons and Liters.</p> <p><strong>Mission Critical</strong> <br /> Mission critical to overseas operations.</p> <p><strong>Benefits</strong> <br /> Reduce conversion time to gallons for every entry and improve data reporting accuracy.</p> <p><strong>Users</strong> <br /> All users serving OCONUS.</p>
20311HRH Role Request01449PADIANewSubmitted: 3/11/2019<p><strong>Description</strong> <br /> Our agency has hand receipt holders, assigned as an additional duty.  The current Custodian roles available in DPAS are too privileged.</p> <p><strong>Recommended</strong> <br /> Create a HRH Role, which has the ability to manage sub custodians.  The role should be able to create sub custodians and move property between the Major Custodian hand receipt and the Sub Custodians.</p> <p><strong>Mission Critical</strong> <br /> This is considered mission critical for our agency. </p> <p><strong>Benefits</strong> <br /> This will allow us to distribute the workload to our hand receipt holders and allow them to manage sub hand receipts.  We can't use existing custodian roles because those allow other operations (transfer, disposal) that our hand receipt holders shouldn't perform.</p> <p><strong>Users</strong> <br /> Only certain users</p>
20310Secure Inventory Reports01448PADIANewSubmitted: 3/11/2019<p><strong>Description</strong> <br /> The generated Inventory reports are editable PDFs.  This makes it possible for a hand receipt holder to possibly remove assets or change information on the report, without updating DPAS data.</p> <p><strong>Recommended</strong> <br /> Add a digital signature field to the signature block on all Inventory reports, and secure the pdf document the same as you have done with the DD Form 200.  Allow printing, filling existing fields, and signing existing digital signature fields.  This could be an option when creating the form.</p> <p><strong>Mission Critical</strong> <br /> Our leadership is concerned with this issue, and we need this capability.</p> <p><strong>Benefits</strong> <br /> This will improve accuracy and accountability.  SIIs are monthly requirements - the field below doesn't allow me to answer "How frequently is this transaction performed by a user?"</p> <p><strong>Users</strong> <br /> Most users in our agency are affected.</p>
20309M & U Upload01447MUArmy: LDACNewSubmitted: 20190308<p><strong>Description</strong> <br /> We need to be able to upload a spreadsheet in to M & U of monthly utilization for each asset that is in M & U.  We need to save some time when inputting monthly utilization.  As we have almost 965 assets.  Inputting each one is very time consuming.  We would like to make it where a spreadsheet is utilized the same as PA module, where you can upload 500 assets at one time.</p> <p><strong>Recommended</strong> <br /> Capability in M & U to upload utilization for assets by a spreadsheet for monthly requirements.</p> <p><strong>Mission Critical</strong> <br /> this is not mission critical. </p> <p><strong>Benefits</strong> <br /> Reduces time/ cost.  Also would improve accuracy, due to the fact that a human is not key punching all the numbers, less chance of errors.  Accountability is improved by less chance of error.</p> <p><strong>Users</strong> <br /> We believe it would benefit all users.  It would save a lot of time and there is less chance of making a mistake.</p>
20308Student Information System / Member Profile Interface01446WarehouseUSAFADoneSubmitted: 06-MARCH-2019<p><strong>Description</strong> <br /> The U.S. Air Force Academy (USAFA) is migrating to DPAS. Due to frequent squadron and duty status changes for Cadets, information within DPAS Member Profiles should be constantly synced with the Student Information System. Duty Status changes can impact what a Cadet may be issued at any given time. Therefore, updates to the Member Profile should occur on a daily basis.</p> <p><strong>Recommended</strong> <br /> A DAAS-GEX automated File Transfer process established wherein USAFA can push Member Profile update files to the DPAS Member Profile table</p> <p><strong>Mission Critical</strong> <br /> Mission Critical: The USAFA business model relies upon updated, accurate tracking of cadets and their associated sales charges throughout the life cycle of the cadet, from In-Processing through graduation. Without timely updates, Cadets may be improperly issued material and equipment if incorrect information is located in the Member Profile tables.</p> <p><strong>Benefits</strong> <br /> Allows for accurate and timely updates of USAFA Cadet Information throughout cadet life cycle, pay deductions for DFAS/FM, and accountability for issued/sold items.</p> <p><strong>Users</strong> <br /> This functionality will affect all users within the USAFA agency.</p> <p><strong>Completed – Release 7.1 – 26 July 2019</strong></p>
20307UIT feed to include all assets from all DPAS modules01445EnterpriseArmy: LDACDoneSubmitted: 6 March 2019<p><strong>Description</strong> <br /> LDAC is not receiving all assets from DPAS in the current  DPAS to LDAC UIT automated interface.  Currently only reportable items within the Property Book module are being sent to LDAC through this interface which is based upon the RICC.  If the RICC is 0, DPAS does not send any equipment on hand quantities or serial numbers to LDAC for asset and UIT reporting.  LDAC is also missing asset data from the other modules within DPAS to include the warehouse module, as well as internal DPAS transactions and external DPAS transactions.</p> <p><strong>Recommended</strong></p> <ol> <li>Remove the filtering of the RICC logic from the UIT interface so that DPAS can begin providing all assets within the property book module to LDAC regardless if they are coded in the catalog as being reportable</li> <li>Provide LDAC the asset on hand quantities, serial numbers and UIIs from the DPAS warehouse module.</li> <li>Provide the internal and external DPAS transactions to LDAC to support Asset Visibility, UIT and DST reporting.</li> </ol> <p><strong>Mission Critical</strong> <br /> Mission critical -This causes a lack of visibility of assets and associated transactions and impacts both LDAC's high viability applications and data shared with trading partners.  Lack of visibility of all assets and transactions within all of DPAS's modules causes Department of Army to make decisions on Army authorizations and forecasting necessary future equipment purchases based on incomplete Equipment on hand data.  This issue also negatively impacts the Lead Materiel Integrator and equipment planners when making equipment moves to fill shortages and can cause unnecessary equipment moves, wasting both time and resources (Second Destination Transportation Costs). </p> <p><strong>Benefits</strong> <br /> Improves Accuracy, Accountability and Visibility of all assets and transactions. Provides a better asset picture to enable decision makers at all levels to make equipping decisions based on more accurate on hand numbers.</p> <p><strong>Users</strong> <br /> Yes</p> <p><strong>Completed – Release 7.2.00 – 8 November 2019</strong></p>
20306SIS Interface01444WarehouseUSAFADoneSubmitted: 22 FEB 2019<p><strong>Description</strong> <br /> The U.S. Air Force Academy (USAFA) is migrating to DPAS for the tracking of supplies and materiel and for its Individual Issue of materiel to its cadets. Some specific required data fields do not currently exist in the DPAS Member Profile tables, and need to be added in order for USAFA to maintain the current business model and processes.</p> <p><strong>Recommended</strong> <br /> DPAS be modified to add data fields to the Member Profile section. Exact fields to be provided to Leidos development team with character requirements.</p> <p><strong>Mission Critical</strong> <br /> Mission Critical: The USAFA business model relies upon updated, accurate tracking of cadets and their associated sales charges throughout the life cycle of the cadet, from In-Processing through graduation. These data points are currently supported and need to be functional and updated in DPAS.</p> <p><strong>Benefits</strong> <br /> Allows for accurate and timely updates of USAFA Cadet information throughout cadet life cycle, pay deductions for DFAS/FM, and accountability for issued/sold items.</p> <p><strong>Users</strong> <br /> This functionality will affect all users within the USAFA agency.</p> <p><strong>Completed – Release 7.1 – 26 July 2019</strong></p>
20305LIN/TAMCN Column Addition01443WarehouseUSMC: CSPRemovedSubmitted: 28 Feb 2019<p><strong>Description</strong> <br /> Currently there is no LIN/TAMCN Column in Manage Physical Inventories>grid Options>Columns.</p> <p><strong>Recommended</strong> <br /> Recommend that the LIN/TAMCN Column in Manage Physical Inventories>grid Options>Columns be added.</p> <p><strong>Mission Critical</strong> <br /> Yes, This will help us identify PIR for each TAMCN when we do multiple locations for each TAMCN in one or the same  warehouse module.</p> <p><strong>Benefits</strong> <br /> Having this functionality will help from having to go through multiple steps to get the information we need for Audit Purposes.</p> <p><strong>Users</strong> <br /> All IIF/UIF</p> <p><strong>23 Sept 2021 - cancelled per Jack Sanders</strong> <br /> No longer needed after the Reconciliation inquiry.</p>
20304Extract Info from DPAS to DRCED01442EnterpriseOSDDoneSubmitted: 26 FEB 2019<p><strong>Description</strong> <br /> Develop an automated capability (API, FTP, etc.) to extract and transmit detailed transaction data from the DPAS platform to the OUSD Universe of Transactions (UoT) Defense Repository for Common Enterprise Data (DRCED).</p> <p><strong>Recommended</strong> <br /> Enhance the existing DPAS Accounting Transactions Report capability to include control totals required by DRCED.  Automatically generate this enhanced report, or data extract, and utilize the existing DPAS GEX channel to deliver this data set to the DRCED DISA SFG Relay.  </p> <p><strong>Mission Critical</strong> <br /> Mandated per Revised Technical Solution for a Defense-wide Appropriations Universe of Transactions Memorandum, 16 Aug, 2016.  This is also a requirement of the DPAS Functional Proponent, DASD Log.</p> <p><strong>Benefits</strong> <br /> Improves Accuracy/Accountability, Financial Reporting.</p> <p><strong>Users</strong> <br /> All DPAS communities' data will be impacted. This is a DoD level requirement.  There will be no disruption to service; only the modified report from DPAS should need to be sent to DRCED.</p> <p><strong>Completed – Release 7.2.00 – 8 November 2019</strong></p>
20303Individual Issue Sales01441WarehouseAF: OtherDoneSubmitted: 12-FEB-2019<p><strong>Description</strong> <br /> The U.S. Air Force Academy (USAFA) is migrating to DPAS for the tracking of supplies and materiel and for its Individual Issue of materiel to its cadets.  Some of the materiel that is issued to a cadet is chargeable to the cadet - either at time of issue, or at a later date in time that it is determined that the cadet is not going to return materiel.  In the past, these charges were exported from our system and sent to DFAS - who is responsible for deducting the applicable amount from the cadet's pay. The DPAS Warehouse application lacks the functionality to produce the appropriate list of charges for each member and to provide those charges to DFAS for gear issued to warehouse members that will not be returned to the warehouse.</p> <p><strong>Recommended</strong></p> <ol> <li>DPAS be modified to allow for the identification of items that are chargeable to the cadet at time of issue or return. </li> <li>The system should allow the USAFA to establish a cost that will be charged by Stock Number using the Moving Average Cost "MAC" of the Inventory or the Current Replacement Cost plus or minus a user controlled "tariff" as the basis that the cadet will reimburse the U.S Government. </li> <li>Provide a process (Listing / Spreadsheet / Electronic Interface if DFAS supports - TBD) where the charges by cadet can be certified by the USAFA and sent to DFAS for collection.</li> <li>Provide a query/report that identifies the amount reimbursed by cadet in total or for a period of time by date issued and what reporting period it was sent to DFAS for collection / reimbursement.  The report should show the item being reimbursed, the date the transaction occurred, who applied the charge and the reason for the charge.</li> </ol> <p><strong>Mission Critical</strong> <br /> Mission Critical: Reimbursement of issues to cadets is a primary function of the US Air Force Academy business model, and is currently a capability of the system being sunset in favor of DPAS.</p> <p><strong>Benefits</strong> <br /> Allows for the proper recording and accounting of the cost of materiel not being returned to the warehouse - improving the accuracy of financial reporting.</p> <p><strong>Users</strong> <br /> This functionality will affect all users within the USAFA agency. </p> <p><strong>Completed – Release 7.1 – 26 July 2019</strong></p>
20302Inventory Sales01440WarehouseAF: OtherDoneSubmitted: 12-FEB-2019<p><strong>Description</strong> <br /> USAFA routinely charges members for materiel they were issued from the warehouse that will not be returned. In the past, these charges were exported from our system to DFAS - who is responsible for deducting the applicable amount from members pay. The DPAS Warehouse application lacks the functionality to produce the appropriate list of charges for each member and to provide those charges to DFAS for gear issued to warehouse members that will not be returned to the warehouse.</p> <p><strong>Recommended</strong> <br /> DFAS is responsible for deducting the cost of the materiel from the members pay. The cost deducted is computed using the Stock Number unit price plus or minus a pre-defined "tariff". Provide a means of computing the applicable cost and the ability to communicate these costs to DFAS for the materiel issued to warehouse members that are non-returnable/lost/damaged.</p> <p><strong>Mission Critical</strong> <br /> Mission Critical: Inventory sale is a primary function of the US Air Force Academy business process and is currently accomplished in the system being shut off in favor of DPAS Warehouse.</p> <p><strong>Benefits</strong> <br /> Allows for the proper recording and accounting of the cost of materiel not being returned to the warehouse - improving the accuracy of financial reporting.</p> <p><strong>Users</strong> <br /> This functionality will affect all users within the USAFA agency</p> <p><strong>Completed – Release 7.1 – 26 July 2019</strong></p>
20301Loan Module Modification01439PAAF: OtherNewSubmitted: 2/11/2019<p><strong>Description</strong> <br /> Loan module only works for serialized managed assets and not for bulk managed assets</p> <p><strong>Recommended</strong> <br /> Modify Loan Module to include bulk managed assets</p> <p><strong>Mission Critical</strong> <br /> This is mission critical and is crucial for GFE and overall tracking of loaned assets.   Currently we have no tracking capability for bulk assets out on Loan.</p> <p><strong>Benefits</strong> <br /> Improved accountability of bulk assets out on loan.</p> <p><strong>Users</strong> <br /> Yes, this will affect all users within our Agency</p>
20300IUS - Funding Identification01438PANavyRemovedSubmitted: 6FEB2019<p><strong>Description</strong> <br /> In the Asset Receiving Module, there is no ability to distinguish the type of funding for various Internal Use Software (IUS). This is critical as capitalization thresholds are different for the various types of IUS. <br /> Currently, the Capitalization threshold for all IUS is $250K. However, the Capitalization threshold for Military Intelligence Program (MIP) and National Intelligence Program (NIP) IUS is $1M. As a result, DPAS will incorrectly capitalize MIP and NIP IUS below the $1M threshold and require the APO to manually change the capitalization code to "N" (Non capital, exceeds threshold) to stop the asset from depreciating.  </p> <p><strong>Recommended</strong> <br /> Develop a programmatic process for DPAS to distinguish between the various types of software capital thresholds and to set the capitalization code for capital thresholds at the correct levels.</p> <p><strong>Mission Critical</strong> <br /> Mission critical/mandated.  DoD 7000.14-R Vol 4, Ch 27 pg 27-18 states " The current IUS capitalization threshold for all DoD Components is $250,000, except for the Office of the Director of National Intelligence, for which the capitalization threshold is $1 million."</p> <p><strong>Benefits</strong> <br /> Ensures that capitalization of IUS is correctly applied per DOD regulation</p> <p><strong>Users</strong> <br /> All Agencies would be affected by this SCR.</p> <p><strong>14Feb2019 – cancelled per Kevin Callahan </strong> <br /> At the request of the BSO (NL-CCAF).</p>
20299IUS - Hosting Environment01437PANavyDoneSubmitted: 02/06/2019<p><strong>Description</strong> <br /> In the IUS Asset Receiving Module, the Hosting Environment Drop Down, on the Asset Entry Tab does not contain all possible scenarios including "Data Center" and "Network".</p> <p><strong>Recommended</strong> <br /> Add Data Center and Network to the Hosting Environment Drop Down menu on the Asset Entry Tab. Recommend obtain input from DPAS User Community to identify other hosting scenarios not currently available.</p> <p><strong>Mission Critical</strong> <br /> Mission critical. If all possible IUS hosting environments are not listed then inaccurate information will be entered into the database potentially causing an audit finding and trouble completing inventories.</p> <p><strong>Benefits</strong> <br /> Increases accuracy of IUS data elements to ensure the hosting environments of the software are reported correctly.</p> <p><strong>Users</strong> <br /> This will affect all agencies.</p> <p><strong>Completed – Release 2021.1.2 – 19 March 2021</strong></p>
20298Scheduling Multiple Lane Types01436WarehouseUSMC: CSPRemovedSubmitted: 1/16/2019<p><strong>Description</strong> <br /> Currently when using the scheduling functionality there isn't a way to assign more than one activity to one lane. We would like to have the option of selecting multiple options for one lane. This would allow us to group all issue or return types to that one lane.</p> <p><strong>Recommended</strong> <br /> Recommend using a multiple select field for lane type assignment. This would allow us to select multiple lane types for one lane. This will be helpful in scheduling all issue and return types to separate lanes in larger warehouses if we choose too.</p> <p><strong>Mission Critical</strong> <br /> This is mission critical because it will allow us to assign multiple lane types to one lane. This would help organize how we assign lanes and make it more efficient.</p> <p><strong>Benefits</strong> <br /> Having the ability to assign multiple lane types would help increase efficiency of how each warehouse lane is used.</p> <p><strong>Users</strong> <br /> This will affect all users who managing the scheduling of lane assignments. This will also affect CSP customers considering that scheduling lane types could change how often appointments are scheduled.</p> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20297Inventory Activity Reason Code01435WarehouseUSMC: CSPNewSubmitted: 01/11/2019<p><strong>Description</strong> <br /> Currently in Inventory Activity there is no ability to select multiple reason codes in the search grid. This becomes problematic when searching for Inventory gains and losses because there are multiple reason codes for these. The only way we are currently able to pull this data is ask the DPASSupport desk to pull the data, or pull all inventory activity data and then filter down. The latter method is time consuming and in most cases unsuccessful because of the amount of data pulled.</p> <p><strong>Recommended</strong> <br /> Recommend that the Reason Code search option be a multi-select field. This would be similar to how the Location Type Code search field works on the Location AUD grid. This would allow for us to select all the inventory adjustments reason codes in one search.</p> <p><strong>Mission Critical</strong> <br /> It has been mandated by LOGCOM leadership that the CSP has the ability to pull these reports and provide them to auditors on a quarterly basis at the very least. Currently, in most cases, the only way we are able to obtain these reports is through DPAS Help Desk request.</p> <p><strong>Benefits</strong> <br /> Implementing these changes increases the accuracy of the data and improves the amount of time it takes to pull reports. It would also make CSP users more self sufficient when obtaining these reports since they will no longer request DPAS Help Desk assistance.</p> <p><strong>Users</strong> <br /> This will affect all CPS users.</p>
20296ICP Stock Item Add01434Materiel ManagementUSMC: CSPRemovedSubmitted: 01/11/2019<p><strong>Description</strong> <br /> In the ICP there is currently no way to add stock number to the stock item AUD for multiple warehouses. To add the new stock number to the stock item AUD for the warehouses we have to do it individually for each warehouse. This is a time consuming process.</p> <p><strong>Recommended</strong> <br /> CSP recommends creating functionality that will allow for user to add stock number to the a stock item AUD for multiple warehouse at a time. This will make it easier for users to add new stock number to the stock item AUD for all warehouses.</p> <p><strong>Mission Critical</strong> <br /> Yes, this will allow for the CSP PMO to add the stock numbers to the stock item list for every warehouse when new stock numbers are introduced to the program.</p> <p><strong>Benefits</strong> <br /> This reduces the time and increases the efficiency when adding stock numbers to the stock item AUD in the ICP.</p> <p><strong>Users</strong> <br /> Yes, this has the potential to affect all CSP users.</p> <p><strong>14Jan2019 – cancelled per Joe Stossel </strong> <br /> This is a duplicate of SCR <a href="index.php/support/system-change-request/details/4/20235/icp-multiple-stock-nbrs">01374</a>.</p>
20295ICP CSP Inquiry Role01433Materiel ManagementUSMC: CSPNewSubmitted: 01/11/2019<p><strong>Description</strong> <br /> Currently when DPAS warehouses are attached to a DPAS ICP they are unable to add stock items to the warehouse. We have tried to give users roles to the ICP in order to add stock items, but this becomes problematic because of the limited number of ICP roles. The current ICP roles give warehouse users too much functionality beyond adding stock numbers to the stock item list.</p> <p><strong>Recommended</strong> <br /> CSP recommends creating a new role that can be granted to users that only has the ability to add stock numbers to the stock item grid. This will give CSP users the required functionality to add stock numbers to the stock item list, but will not let them view or transact elsewhere in the ICP.</p> <p><strong>Mission Critical</strong> <br /> Yes, currently in the CSP program,  users must contact users who have ICP access in order to get stock numbers added. There are very limited number of users who have this access which could possible cause a work stoppage.</p> <p><strong>Benefits</strong> <br /> The benefits of implementing this solution is that we could assign users in every warehouse this role. This would allow every warehouse to be self sufficient when adding stock numbers to their stock item list.</p> <p><strong>Users</strong> <br /> Yes this will affect all ICP users who will be assigned this new role.</p>
20294New Form in Unit Issue Request and Transfer Process01432WarehouseNAVAIRNewSubmitted: 19 DEC 2018<p><strong>Description</strong><br /> The existing ST/STE database, eTIMS, generated a form called a "C-List" for every request created. The "C-List" contained: who created the request, who the list is addressed to (warehouse if a unit issue request, or vendor if an issue transfer), request number, date request created, aircraft, comments (remarks), ST/STE list, contract, UIC, expected return date, ship to (UIC and address), ship to contact (name and phone). The closest thing to this form in DPAS is the Issue Receipt form. This form does not have some information which used to be on the "C-List." Also, the Issue Receipt is only available once a UIR is Issued. NAVSUP WSS requires a form be generated upon the completion of a UIR on their end (once the UIR's status changed to PK-Picking). As of now, they have to take screen shots of the UIR page to provide to PCOs and vendors to show we have completed the request. A sample C-List from eTIMS and an example of what the new form should look like will be provided with the submittal of this SCR.</p> <p><strong>Recommended</strong><br /> Create a new form that includes all information as the provided C-List, or update the Issue Receipt to include this information.  The information that should be included on the form should be: Unit Issue Request Established By, Established Date/Time, To, Request or Transfer #, Reportable Commodity Type, Remarks (mainly for TAC information), Tooling List, UIC, Account Name, Expected Return Date, Ship to Address, and Contact Information of UIC Custodian.  Make this form available to view and print when the request is "In-Process" or "Pk-Picking" status. Also make this form available during the Unit Issue Transfer process.</p> <p><strong>Mission Critical</strong><br /> Mandated. Vendors and PCOs require some type of documentation to use as a receipt that the UIR has been started/completed. DCMA uses this documentation when inspection occurs, PCOs use this document when modifying their contracts.</p> <p><strong>Benefits</strong><br /> This solution will create a formal document that we can use as proof of completing a UIR. It will improve accountability and standardize the UIR process.</p> <p><strong>Users</strong><br /> This change will impact not only users of DPAS and the ST/STE community, but DLA, NAVSUP WSS, and NAVAIR PCOs/ACOs. Vendors also rely on a formal document as an inspection point that a UIR has been completed.</p>
20293View Asset Additional Information in ICN Inventory01431WarehouseNAVAIRNewSubmitted: 19 DEC 2018<p><strong>Description</strong><br /> Some users can add Additional Information to an ICN during receiving and in Inventory Update; however, there is no other place to view this information.  Not all users have or need access to Receiving or Inventory Update.  Additional Information needs to be available to view on the ICN Inventory Inquiry so that all users can read/review the Additional Information.</p> <p><strong>Recommended</strong><br /> Recommending the ability to view asset "Additional Information" as found in Inventory Update in ICN Inventory Grid Options.  Recommending this to also be a searchable field.</p> <p><strong>Mission Critical</strong><br /> Not mission critical or mandated.</p> <p><strong>Benefits</strong><br /> This will improve accuracy and accountability of the tools by being able to see relevant notes to specific tools that users have entered so other users with different roles can see.  The notes will also leave a history for the tool to further help in the case of tool history research.</p> <p><strong>Users</strong><br /> It will affect all users because notes for the specific tool will be seen by all.</p>
20292Update Expected Return Date01430WarehouseNAVAIRNewSubmitted: 19 DEC 2018<p><strong>Description</strong><br /> There are 3 categories of ST/STE requests:</p> <ol> <li>Warehouse requests (ST/STE is stored at a warehouse and is requested to be shipped to a location for usage),</li> <li>Contract Transfers (ST/STE is staying at the current location, but changing its contract accountability),</li> <li>Loan Extensions (ST/STE is staying at the current location and being used under the current contract, but the expected return date needs changing).</li> </ol> <p>The Unit Issue Request process works well for warehouse requests. However, for Contract Transfer Requests, utilizing the existing Unit Transfer Request process does not give us the ability to update the expected return date. There also isn't a separate process to allow for updating return dates when processing Loan Extension requests.  Lastly, Open Warehouse Actions for Unit Returns are not updating when an expected return date is updated.<br /> The work around we have been using in order to add return dates is to return ST/STE to the warehouse, then issue it back out with a Unit Issue Request with a return date. This is creating unnecessary rework and longer touch times and cycle times to complete requests.</p> <p><strong>Recommended</strong><br /> Incorporate the ability to add an expected return date to the Unit Transfer Request process and the ability to update the expected return date to ST/STE on loan (without transferring the contract). Accommodate the Contract Transfer and Loan Extension Requests described above.  Open Warehouse Actions for Unit Returns need to be updated when expected return dates are updated.</p> <p><strong>Mission Critical</strong><br /> Mission critical. ST/STE must have accurate expected return dates in order to have proper accountability and traceability.</p> <p><strong>Benefits</strong><br /> This implementation should reduce the cycle time to complete Unit Transfers and Loan Extensions by at least 67%.</p> <p><strong>Users</strong><br /> This change will impact not only users of DPAS and the ST/STE community, but it will improve fleet readiness by allowing us to complete requests much faster than we currently do.</p>
20291Expanding Stock Number Field01429EnterpriseNAVAIRNewSubmitted: 19 DEC 2018<p><strong>Description</strong><br /> NAVAIR is responsible for managing Special Tooling/Special Tooling Equipment associated with various weapon systems/reportable commodity types.   Manufacturing numbers that are created by vendors are used for the stock numbers of the tools.  However, the vendors' manufactured numbers have been known to be 25+ long.  The length of these numbers are not standardized across vendors.  More than 15 characters are assigned to ST/STE to uniquely identify the tool.  As such the current solution prevents the use of the Stock Number field and the associated capability within the DPAS system.   The Special Tooling Identifier is part of the Stock Number Description Field along with the Noun.  In addition, this practice makes it difficult to utilize the Master List Capability to building Tool to Tool and Tool to Part relationships.<br /> The conversion into DPAS utilized a unique identifier from the source systems primary key, but after conversion future entries will require the generation of a unique DPAS key.  Loading large numbers of ST/STE from OEM will be further complicated as the OEM assign the Tool ID and the current practice of using the Stock Number Description will not trap duplicate entries on the Catalog.</p> <p><strong>Recommended</strong><br /> Request the expansion of the current 15 character limit of the Stock Number field to 30 characters in the Warehouse Module to accommodate future Special Tooling and Special Tooling Equipment (ST/STE).</p> <p><strong>Mission Critical</strong><br /> Mission Critical.  Over time the management of ST/STE by NAVAIR will be hampered with duplicate Catalog entries due to the 15 Character limit in the Stock Number field.  Future assignment of Inventory to the catalog and asset reporting will be hindered.  Duplicate Stock Number entries (via a description) will challenge audit-ability of this data.</p> <p><strong>Benefits</strong></p> <ol> <li>Tight control of the Tooling Catalog</li> <li>Reduce workload on finding tooling associated with weapon system BOMs</li> <li>Full benefit and reporting capability offered by the Stock Number Field</li> <li>Easier loading of future PPSA files</li> <li>Elimination of duplicate Catalog entries and association of Inventory to Catalog entries, removal of future audit findings.</li> </ol> <p><strong>Users</strong><br /> This change will impact current Navy ST/STE community and potentially the Air Force ST/STE community.  Additionally any future or current community for which the Stock Number field proves to be too short.</p>
20290Customer/Unit ID00638MUOSDRemovedSubmitted: 5/27/2014<p><strong>Description</strong><br /> Under Mass Data, desire a Customer/Unit ID field to identify a POC name, email address and telephone number.  (Not a Mandatory Field)  This will reduce the number of 'Dispatched To' names that show up during Dispatch.  Currently every operator loaded in DPAS appears making the search cumbersome.  This improvement will reflect operators from Customer ID or Cost Center only. </p> <p><strong>Recommended</strong><br /> With Cust/Unit ID, we can associate customer for Recurring Dispatch, only pull operators associated with Customer ID during Dispatch and notify POC via email for Pending/Recall work orders.</p> <p><strong>Mission Critical</strong><br /> Streamlines Dispatch functionality for unit issuing.</p> <p><strong>Benefits</strong><br /> Reduces time for vehicle assignment and allows for a more accurate management and assignment of assets.</p> <p><strong>Users</strong><br /> M&U and Dispatch Officer</p> <p><strong>07Dec2018 – cancelled per Deric Sims </strong> <br /> No longer needed due to past enhancements.</p>
20289Calculate Indirect Labor Rate01428MUAF: VSCOSNewSubmitted: 11/16/2018<p><strong>Description</strong> <br /> Currently, DPAS does not provide an indirect labor rate.  Indirect labor rate should include  all work performed by civilian and military personnel charged to the transportation function that cannot be identified to a particular NTV or group of NTVs. </p> <p><strong>Recommended</strong> <br /> Utilize work order reasons; "PORL - Parts Only Low Cost Bench Stock" and create a work order reason "INDR - Indirect Labor".  Calculate by dividing total indirect labor cost by total available direct cost.</p> <p><strong>Mission Critical</strong> <br /> This mandated per DoD 4500.36, Appendix 2 Enclosure 4</p> <p><strong>Benefits</strong> <br /> The benefits of this solution would be to solidify the correct indirect labor rate across all DoD functions.</p> <p><strong>Users</strong> <br /> All DoD Fleet Managers/Maintenance controllers and Material specialists utilize this information for day to day fleet management purposes.  </p>
20288Asset Visibility Report01427WarehouseSPECWARCOMDoneSubmitted: 11/15/2018<p><strong>Description</strong> <br /> No ability to see asset visibility within our LP or Warehouse</p> <p><strong>Recommended</strong> <br /> Create a new asset visibility real time report</p> <p><strong>Mission Critical</strong> <br /> yes.</p> <p><strong>Benefits</strong> <br />  </p> <p><strong>Users</strong></p> <p><strong>Completed – Release 6.3 – 21 December 2018</strong></p>
20287Calculate Asset End of Life01426MUAF: VSCOSNewSubmitted: 11/14/2018<p><strong>Description</strong> <br /> Currently DPAS does not calculate an assets end of life (EOL) when its average annual sustainment cost first exceeds, or is projected to exceed, its depreciated value, or seven years after a depot rebuild, whichever comes later.</p> <p><strong>Recommended</strong> <br /> See notes below.  This feature was developed by 441 VSCOS and added to LIMS-EV Transaction Request Tool. </p> <p><strong>Mission Critical</strong> <br /> Mission critical.  AFI 24-302 states "Use economical, reliable and up-to-date procedures to authorize, acquire, account for and maintain vehicles in a safe and serviceable condition throughout their lifecycle."  The EOL calculation helps determine the most economical time to replace an asset.</p> <p><strong>Benefits</strong> <br /> The benefits of implementing this solution will enhance the annual vehicle purchase drill be pin pointing the most economical time to replace an aging asset.</p> <p><strong>Users</strong> <br /> All Air Force Fleet Managers/Maintenance controllers and Material specialists utilize this information for day to day fleet management purposes.  </p> <p><strong>**NOTE**</strong> This SCR is in conjunction with <a href="index.php/support/system-change-request/details/4/20283/vehicle-prioritization-model">SCR 01422 </a>Vehicle Prioritization Model.</p>
20286IntelliSense for Operators01425MUOSDNewSubmitted: 11/14/2018<p><strong>Description</strong> <br /> Operator / Technician listing is very long and slows down the assignment process in Dispatch.  There is no quick way of finding an individual.</p> <p><strong>Recommended</strong> <br /> Utilize the IntelliSense capability when assigning "Dispatched To" during the Dispatch A/U.</p> <p><strong>Mission Critical</strong> <br /> Critical to the accurate and expedient assignment of personnel to equipment</p> <p><strong>Benefits</strong> <br /> Reduces time and improves accuracy of asset assignment.</p> <p><strong>Users</strong> <br /> Only personnel identified to accept material via M&U.</p>
20285DPAS Account Status01424EnterpriseOSDNewSubmitted: 11/14/2018<p><strong>Description</strong> <br /> The Agency has no way of monitoring user activity to ensure accounts stay active.</p> <p><strong>Recommended</strong> <br /> Request adding to Accounts Status to the Inquiry of the IO, APO, M&U Officer and M&U Dispatch Officer roles.  Currently activities task DPAS Security to produce report for them.</p> <p><strong>Mission Critical</strong> <br /> Critical to mission by ensuring accounts remain active especially for the National Guard and Reserve Units</p> <p><strong>Benefits</strong> <br /> Ensure users with sporadic work schedules maintain active accounts and will not spend time reactivating them.</p> <p><strong>Users</strong></p>
20284Cost Center Use in M&U01423MUOSDNewSubmitted: 11/14/2018<p><strong>Description</strong> <br /> In PA, Cost Centers can be created for each asset.  It would be efficient to have that migrate to M&U for reimbursements for Work Orders and Dispatch</p> <p><strong>Recommended</strong> <br /> If created in PA, use the Cost Center as the Flag for reimbursement.  This will give another level of identification for funding and will automatically be assigned to assets in M&U.</p> <p><strong>Mission Critical</strong><br /> No</p> <p><strong>Benefits</strong> <br /> Improves the process of identifying costing source for WO and Dispatch.</p> <p><strong>Users</strong></p>
20283Vehicle Prioritization Model01422MUAF: VSCOSNewSubmitted: 11/13/2018<p><strong>Description</strong> <br /> Currently, DPAS cannot differentiate life expectancies for all assets to determine the appropriate replacement cycle necessary for programming purposes. The Vehicle Prioritization Model provides better justification for appropriations and is a proven business model that identifies vehicle requirements while connecting them with the mission they support.</p> <p><strong>Recommended</strong> <br /> See notes below.  This feature was developed by 441 VSCOS and added to LIMS-EV Vehicle View.</p> <p><strong>Mission Critical</strong> <br /> Mission critical.  AFI 24-302 states "Use economical, reliable and up-to-date procedures to authorize, acquire, account for and maintain vehicles in a safe and serviceable condition throughout their lifecycle."  The Vehicle Prioritization Model helps determine the most economical time to replace an asset.</p> <p><strong>Benefits</strong> <br /> The benefits of implementing this solution will enhance the annual vehicle purchase drill by pin pointing which asset to replace at the most economical time.</p> <p><strong>Users</strong> <br /> All Air Force Fleet Managers/Maintenance controllers and Material specialists utilize this information for day to day fleet management purposes.  </p> <p><strong>**NOTE**</strong> This SCR is in conjunction with <a href="index.php/support/system-change-request/details/4/20287/calculate-asset-end-of-life">SCR 01426 </a>Calculate Asset End of Life</p>
20282WAWF/IRAPT Updates01421EnterpriseLeidosNewSubmitted: 11/14/2018<p><strong>Description</strong> <br /> When Wide Area Work Flow (WAWF) initially implemented an interface with APSRs, the intent was to provide Receiving Report data for New Procurements, and provide the capability for APSRs to track and confirm receipt of GFP/GFM shipments to contractors utilizing the "TS" functionality.  Utilizing the interface for transfers provided for an auto update of the IUID registry of transfers between the government and contractor. To support this activity, WAWF provided a pseudo DLMS 856S via GEX.  WAWF does not actually generate or receive the DLMS 856S, but rather used GEX's translation service to put the data into the 856S format or to extract the data from the 856S format.  During a recent WAWF Requirement meeting, it was discovered that WAWF has since implemented the DLMS 861 Transaction Set for materiel acceptances rather than using the DLMS 856S.  This was not known to DPAS as DPAS believed it was receiving acceptance notices via the DLMS 856S.  A review of the DLMS transactions DPAS received in 2017, it does appear that DPAS does in fact receive materiel acceptance via the 856S transaction set.  The WAWF Program believes DPAS should transition to the DLMS 861 for Acceptance.  During the review, it was discovered that DPAS is not capturing the "Acceptance Dt".  Everything is being driven by the Receipt Dt.   </p> <p><strong>Recommended</strong> <br /> Review current WAWF processing and determine whether DPAS should transition to the DLMS 861 Transaction Set for materiel acceptance.  If it should, then make the necessary changes to provide for the receipt and procssing of the DLMS 861 Transaction Set.  Regardless of the outcome of the review (Implement the DLMS 861 or stay with the DLMS 856S), DPAS should be basing the Property Book  / Warehouse Receipt based upon the Acceptance Dt, not the Receipt Dt.  This change should be implemented regardless of the transaction set the Acceptance Dt is acquired from. </p> <p><strong>Mission Critical</strong> <br /> This SCR is considered essential for DPAS compliance with DoD Policy.</p> <p><strong>Benefits</strong> <br /> DPAS maintains its compliance with DoD Policy</p> <p><strong>Users</strong> <br /> This SCR would affect any customer that utilizes the WAWF/IRAPT interface.</p>
20281Update Upcoming Maint Report to Include Miles/Make Self Generated Work Order Optional01420MUAF: VSCOSNewSubmitted: 9 Nov 2018<p><strong>Description</strong> <br />Currently, there is no way to run a report or inquiry that identifies assets that are due scheduled maintenance with intervals by mileage.  Additionally, the self generated work order makes managing the scheduled work load cumbersome because of the possibility of several work orders being opened for the same asset ID.</p> <p><strong>Recommended</strong> <br /> Update Upcoming Work Report to include a column and indicator that identifies an asset as within its scheduled maintenance window per the "Sched Before Util Qty" field.  The indicator would be the mileage difference between "Util Qty Frequency" and "Sched Before Util Qty".  If the asset has no scheduled maintenance intervals due, it will not display on the report.  Also, we need a feature to disable the system generated work order.  A check box; Auto Generate Work Order Y/N?   This will give the maintenance scheduler the ability to decide on how to assign/document scheduled maintenance actions.</p> <p><strong>Mission Critical</strong> <br /> This is mission critical.  AFI 34-302 states "Scheduled maintenance includes PM&I and Special Inspections, at regular intervals to maintain a safe and serviceable vehicle fleet."</p> <p><strong>Benefits</strong> <br /> The benefits of implementing this solution would be a more streamlined and user friendly scheduled maintenance program.</p> <p><strong>Users</strong> <br />All Air Force Fleet Managers/Maintenance controllers and Material specialists utilize this information for day to day fleet management purposes.  </p>
20280Air Force Prior Day Report01419MUAF: VSCOSNewSubmitted: 9 Nov 2018<p><strong>Description</strong> <br /> Currently, there is not a easy way to see what transactions in the M&U DPAS module that have been completed on a daily basis. So managers can review and make any edits as needed.</p> <p><strong>Recommended</strong> <br />DPAS the ability to produce a Prior Day Edit Report, when requested with the following perimeters in the fields:</p> <ul> <li>Work Order inputs (# open, # closed) with Work Order # and Asset #,</li> <li>Labor Hour inputs by Work Order # and Sub Work Order #,</li> <li>Work Plans associated.</li> </ul> <p>Parts charged to include:</p> <ul> <li>work order #,</li> <li>cost,</li> <li>nomenclature & quantity,</li> <li>and warranty.</li> </ul> <p>Parts ordered with:</p> <ul> <li>work order #,</li> <li>quantity,</li> <li>nomenclature,</li> <li>and est cost.</li> </ul> <p>All Utilization updates and the data to go with the:</p> <ul> <li>Asset Id,</li> <li>Meter Reading inputted,</li> <li>Fuel Qty,</li> <li>Fuel Cost,</li> <li>Fuel State.</li> </ul> <p><strong>Mission Critical</strong> <br /> This is critical.  Fleet managers count on viewing information to be able to make informed decisions to manage Air Force fleets around the globe. Also, per AFI 24-302, daily work orders and transactions need to be reviewed and corrections be made to, if needed.</p> <p><strong>Benefits</strong> <br /> Having this Prior Day Report will enhance day to day operations for the Air Force fleet. Also, this will ensure UICs are compliant with AFI 24-302 on daily requirements.</p> <p><strong>Users</strong> <br />This SCR will affect the entire AF Agency, all Air Force fleet managers/maintenance controllers utilize this information for day to day fleet management operations.  </p>
20279ICP ADDED COLUMNS01418Materiel ManagementUSMC: CSPRemovedSubmitted: Nov 07, 2018<p><strong>Description</strong> <br /> During the past ICART Audit Readiness Inspection for the CSP it was noted that extra Columns are needed to be added to the Inventory Control Point>DLMS Transaction Inquiry Review area to make the CSP compliant with the current Marine Corps Audit Readiness policies. </p> <p><strong>Recommended</strong> <br /> In order for CSP to be compliant with the current Marine Corps Audit Readiness program we are requesting that the Below columns be added to the following area Inventory Control Point > DLMS Transaction Review:</p> <ul> <li>WAREHOUSE DODAAC</li> <li>USER ID (who created the Transaction)</li> <li>Serial Number</li> </ul> <p><strong>Mission Critical</strong> <br /> Yes, without these columns the CSP is not in compliance with the current Marine Corps Audit Readiness Program.  DoD mandated audits are high visibility and compliance is critical to CSP success. </p> <p><strong>Benefits</strong> <br /> Having this functionality will help the CSP be in compliance with the current Marine Corps Audit Readiness Program.</p> <p><strong>Users</strong> <br /> ICP MODULE</p> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20278Change Acq Dt to Funds Obligation DT01417PANavyNewSubmitted: 5 Nov 2018<p><strong>Description</strong><br /> The "Acquisition Date" field in DPAS is inconsistent with the definition of the term in DPAS, "The date of fund approval / obligation". As the field is titled, "Acquisition Date", most users record the date the asset was received or even ordered. Very few people inherently equate the acquisition date to be the fund obligation date. Because of the ambiguous nature of this term, and the fact that users typically do not use the DPAS glossary to find out what each field is actually requesting, it has resulted in multiple inconsistencies which have basically made this field misused from a data management perspective.</p> <p><strong>Recommended</strong><br /> Change the "Acquisition Date" field in DPAS to "Funds Obligation Date". This change would align the existing definition of the field to the name of the field and reduce confusion for users.</p> <p><strong>Mission Critical</strong><br /> No.</p> <p><strong>Benefits</strong><br /> Improves data accuracy of financial reporting and identifies the funds obligation date from the funding documents, showing auditors the true date when the government committed funds to the order. This would also provide a much clearer understanding for the users out in the field.</p> <p><strong>Users</strong><br /> This affects all DPAS PA module users.</p>
2027733A - RFID01416EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 33A = The Army requires the capability for RFID integration for shipping and receiving (store, field, inv) with TCN per MIL STD 129 requirements for passive tags.</p> <p><strong>Recommended</strong><br /> Collect TCN/Expand current RFID Capability</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong></p> <p><strong>Users</strong><br /> ALL</p>
2027632A - DOUBLE01415EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 32A = GENERATE A MONTHLY REPORT OF "DOUBLE" COUNT ITEMS - EQUIPMENT IN DPAS VS GCSS-A/LMP</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
2027531A - MNTC HIST01414EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 31A = ASA(ALT) requires the ability to be able to track and transfer maintenance record history to the receiving unit.</p> <p><strong>Recommended</strong><br /> requires an Army enterprise wide CR as well</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
2027430A - AOAP01413EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 30A = ASA(ALT) requires the ability to track oil sample intervals.  ASA(ALT) requires the ability to track oil sample results.  Upload/attach the report documentation</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
2027329A - LPDS01412EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 29A = GENERATE A HR BOM TO FEED INTO LPDS</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
2027228A - MDL01411EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 28A = INCLUDE A CODE IN THE CATALOG FOR THE MASTER DIVESTITURE LIST CODE, BLOCK ITEMS FOR RELEASE BASED ON THE CODE, NOTIFY THE PERSON TRYING TO MOVE INVENTORY AS TO THE MDL STATUS</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
2027127A - PQDR01410EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 27A = ASA(ALT) requires the system to generate a PQDR and store the PQDR number, notify mailing list created by the PM/Warehouse</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
2027026A - WO SPARES01409EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 26A = change/transfer part on work order to another after its been requisitioned without canceling the requisition - as long as it doesn't change type of funds OR if it does determine if there is a method to "pay" the other fund back.</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
2026925A - IUID APPS01408EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 25A = IUID Application linkage.  Interface/adopt the use of existing HQDA G-8 IUID applications (PQDRs, registration, etc).</p> <p><strong>Recommended</strong><br /> Expand the ability to interface with DPAS to use mobile apps in lieu of tethered scanners.</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
2026824A - IUID REG01407EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 24A = REQUIRE THE ABILITY TO SWAP PARTS WTIHIN AN ASSEMBLY OR KIT WITH UII AND REPORT THAT PARENT/CHILD RELATIONSHIP CHANGE TO THE REGISTRY</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
2026723A - DOC ADD01406EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 23A =   Need the capability to upload documents to the shipment/issuance/MRO. </p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong><br /> No</p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability</p> <p><strong>Users</strong><br /> ALL</p>
2026622A - SYSTEM OF SYSTEM01405EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 22A = The Army requires the capability to use AIT to build a system-of-systems configuration-tree with scan ability for SIM items and sub-items and system prompts (click button) to confirm qty and NSN/MANP for non-SIM items (aka "assemble of fielding package"; more than one end-item separately classified/authorized but are to be fielded together)</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong><br /> MISSION CRITICAL - PMS FIELD SOS TO SUPPORT CAPABILITY DOCUMENTS</p> <p><strong>Benefits</strong></p> <p><strong>Users</strong><br /> ALL</p>
2026521A - SHIP CHANGE01404EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 21A = Ability to change ship to location in mass</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
2026420A - CONTRACT WRITING01403EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 20A = Method for DPAS to send PR to contract writing system (SPS, PADDS, ACWS, PD2 send to each other?) and receive the signal from WAWF tied to the PR/PO for receipt.</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong><br /> Mission Critical</p> <p><strong>Benefits</strong><br /> Reduces Cost<br />Improves Accuracy<br />Increases Accountability</p> <p><strong>Users</strong><br /> ALL</p>
2026319A - SOFTWARE/HARDWARE01402EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 19A = 1. The Army requires the capability to tie the procurement of software to various hardware combinations; <br />2. need to be able to field hardware with software and track the version of software that's been fielded; <br />3. requires the capability to manage software upgrades;<br />4. track software and the hardware associated by customer (DODAAC) to facilitate required upgrades/updates to that software and hardware; <br />5. needs the capability to install GOTS software on the hardware "in-house" </p> <p><strong>Recommended</strong><br /> CAPABLE IN THE PA MODULE, NEED TO BE EXTENDED TO WAREHOUSE</p> <p><strong>Mission Critical</strong><br /> No</p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability</p> <p><strong>Users</strong><br /> ALL</p>
2026218A - AIRCRAFT NOTEBOOK01401EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 18A = TIE IN AIRCRAFT NOTEBOOK INFORMATION INTO DPAS (SEND/RECEIVE)</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
2026117A - QUERY UII01400EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 17A = AIT scanners search inventory by UII, part#, serial#, item descr, NSN (need to add UII)</p> <p><strong>Recommended</strong><br /> Add UII to existing scanner search</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong></p> <p><strong>Users</strong><br />ALL</p>
2026016A - EXPENDITURE01399EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 16A = ASA(ALT) requires the ability to look at hours spent, how much funds are left for the effort, obligations spent, and plan to actuals. </p> <p><strong>Recommended</strong><br /> TIE CIP TO M&U</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br />ALL</p>
2025915A - AUDIT REPORT01398EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 15A = create a canned report for auditors based on standard questions option to deselect questions (need questions from ASA ALT, SOCOM)</p> <ul> <li>Depreciation Code (indicates capital verses non-capital in DPAS)</li> <li>UII</li> <li>Serial Number</li> <li>Description</li> <li>Material (Stock Number in DPAS)</li> <li>Owner-related data elements (i.e. UIC/ Cost Center in GCSS-Army)</li> <li>Location-related data elements (to me, this should be Plant/ SLOC in LMP/ GCSS-Army)</li> <li>Status/ Condition Code</li> <li>Disposal Date, if applicable</li> <li>Acquisition Date (i.e. Placed in Service Date (PISD))</li> <li>Acquisition Value</li> <li>Useful Life</li> <li>Accumulated Depreciation </li> </ul> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
2025814A - DST01397EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 14A = Link DPAS Due-Ins/Delivery from WAWF to the Army DST</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
2025713A - MMIS01396EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 13A = NEED THE ABILITY TO RECEIVE INPUT FROM MMIS FOR MWOS, AS WELL AS SEND THE NOTIFICATION OF APPLICATION INTO THE MMIS</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
2025612A - FUNDING 101395EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 12A = ASA(ALT) requires the ability to allocate different funding streams to PM mission activities.  track cost in M&U by fund type and/or LOA</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
2025511A - PRINT LABELS01394EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 11A = The Army requires the capability to print/reprint barcodes (UII labels) with std info on 1348-1, 129 Pkg Label, 1387/1149, bin location, pick-ticket info, part  for box, serial # for box, serial # for item</p> <p><strong>Recommended</strong><br /> Add 129 Packaging Label and 1387 to already existing items.</p> <p><strong>Mission Critical</strong><br /> No - Needed in order to minimize the amount of manual paperwork required</p> <p><strong>Benefits</strong><br /> Reduces time<br />Improves accuracy</p> <p><strong>Users</strong><br /> All users within ASA(ALT) will benefit from this action.</p>
2025410A - DLA Warehouse01393EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 10A = Move PM inventory and visibility from DLA warehouse (item, project code to location)</p> <p><strong>Recommended</strong><br /> Can DPAS support ADC 1198?</p> <p><strong>Mission Critical</strong><br /> Mission Critical</p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
202539A - PROJECT CODE01392EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 8A = workflow process for project code changes</p> <p>When ownership of an Army owned material needs to be changed, the inventory needs to be issued from the OWNER 1 TO OWNER 2 containing the current Owner RIC and received back into inventory containing the new Owner RIC. <br />For storage locations that interface with DLMS (LMP, DLA, Contractors, and PM Staging locations that use third party software), the following transactions will be required.  <br />An outbound DLMS (A5_) should be generated to the storage location containing the current Owner RIC. <br />(The ship-to (SUPP ADD) on the outbound A5_ should be the same as the storage site that the A5_ was sent to.) <br />An outbound DLMS (DW_) should also be generated to the storage location to identify the new Owner RIC. <br />An inbound DLMS (AR0) should be received in which will issue the inventory from the current Owner RIC. <br />An inbound DLMS (D6_) should be received which will receipt the inventory into dpas under the new Owner RIC.</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong><br /> Mission Critical</p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
202527A - SKO01391EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 7A = ALLOW MULTIPLE CONFIGURATIONS UNDER ONE MATERIEL NUMBER SKO<br />PERMIT ONE ORGANIZATION TO HAVE A DIFFERENT SET OF QUANTITIES IN A CONFIGURATION THAN ANOTHER ORGANIZATION</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
202516A - AESIP01390EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 6A = UPDATE EXCHANGE WITH AESIP TO EXPAND TO A 2-WAY EXCHANGE.  SUBMISSION/RECEIPT. </p> <ol> <li>CHECK AESIP</li> <ol style="list-style-type: upper-alpha;"> <li>IF YES, ALLOW USE</li> <li>IF NO, CHECK FLIS</li> <ol style="list-style-type: lower-alpha;"> <li>IF YES, VALIDATE ARMY USER - GENERATE JLC FORM</li> <li>IF NO, REQUEST A MANP/MCN/NIIN AS NEEDED BY THE USER</li> </ol> </ol> <li>IF NEED TO REQUEST A MATERIEL NUMBER</li> <ol style="list-style-type: upper-alpha;"> <li>GENERATE CHECKLIST TO DETERMINE IF A "TEMPORARY MATERIEL NUMBER" CAN BE USED</li> <li>IF OUTSIDE A 90 DAY WINDOW - REQUEST EMAIL ADDRESS TO NOTIFY THEM WHEN PART AVAILABLE</li> </ol> </ol> <p><strong>Recommended</strong><br /> OR SOMETHING LIKE THE ABOVE</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
202505A - LMP DLMS01389EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 5A = Require the ability to push and pull inventory from LMP (using project code inventory) using DLMS.</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong><br /> Mission Critical</p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
202494A - BULK LABELS READ01388EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> The Army needs the ability to do break-bulk and verify individual serial numbers against outer pack label.  This needs to tie into the use of AIT devices.</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong><br /> Mission Critical - too many items are packaged with S/N and UII - costly to break the box open to record all of the packed items within the crate.  Scanning external barcode will allow for all items to be receipted without additional packaging costs.</p> <p><strong>Benefits</strong><br /> Reduces time<br />Reduces packaging costs<br />Improves Accountability of inventory within the crates.</p> <p><strong>Users</strong><br /> All users within ASA(ALT) will benefit from this action.</p>
202483A - Virtual W/H01387EnterpriseArmy: ASA(ALT)DoneSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 3A = Requires the ability to bulk ship materiel and break apart on ground and generate issue doc after its been shipped (tie into unit issue MRO, but eventually MRO and leave books)</p> <p><strong>Recommended</strong><br /> Potentially use a virtual warehouse</p> <p><strong>Mission Critical</strong><br /> No</p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p> <p><strong>Completed – Release 2020.1 – 6 March 2020</strong></p>
202472A - EDA01386EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 2A = contract data pull from EDA for all information, create a hyperlink back to contract script, generate due-ins into the warehouse, and pull "smart form" of GFP in annex J so this will feed to "select" from the approved GFP list  - all in the Warehouse</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong><br /> MANDATED - ALL GFP MUST BE TRACKED, CREATING DUE INS TO RECEIPT AGAINST FEED FROM WAWF</p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
202461A - AEMM01385EnterpriseArmy: ASA(ALT)NewSubmitted: 01 Nov 18<p><strong>Description</strong><br /> 1A = Ability to query army equipment master and create if not there (AESIP)</p> <p><strong>Recommended</strong><br /> how does GCSS-A do today; after new receipt of asset also creating record (does WAWF already send? Or DPAS send)</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Improves Accuracy<br />Increases Accountability<br />Decreases time</p> <p><strong>Users</strong><br /> ALL</p>
20245Add attachments to deleted assets01384PANavyRemovedSubmitted: 19 October 2018<p><strong>Description</strong><br /> You cannot add attachments to assets removed after processing a disposition transaction has taken place.  Often APO's forget to attach key supporting documents to asset records before the disposition transaction is processed.  </p> <p><strong>Recommended</strong><br /> Provide functionality to add attachments to delete assets:</p> <ol> <li>Multiple attachments to a single or multiple deleted asset record.</li> <li>A single attachment to a single or multiple deleted asset records.</li> </ol> <p><strong>Mission Critical</strong><br /> Navy FIAR control points require supporting disposition documentation be attached to asset records to include:  key supporting documents (DD 1348/DD 1149) and key supplemental supporting documents in support of audit reviews.</p> <p><strong>Benefits</strong><br /> Supports documentation for accountability and audit.</p> <p><strong>Users</strong><br /> All Navy Site ID's and UIC's.</p> <p> </p> <p><strong>22Oct2018 – cancelled per Randy Reed </strong> <br /> This is the same SCR as <a href="index.php/support/system-change-request/details/4/14066/add-attachments-to-deleted-assets">00858</a> – TFS 14066.</p>
20244Bulk Mileage Upload Rpt01383MUOSDNewSubmitted: 04 October 2018<p><strong>Description</strong><br /> Create a Mileage Report for Lease Code 'D' assets that can be run monthly to capture meter readings recorded in DPAS for transfer to GSA Mileage Express.</p> <p><strong>Recommended</strong><br /> DPAS produce a text file to be pasted in GSA Fleet Drive-thru>Mileage Express>Monthly Mileage Bulk Upload in the following construct: Asset ID, Meter Reading to match Upload file from GSA (attached).</p> <p><strong>Mission Critical</strong><br /> Mission critical and mandated for GSA vehicles since lease cost is dependent of miles driven.  Users are currently capturing mileage to two systems.</p> <p><strong>Benefits</strong><br /> Reduce time and improve accuracy from dual entry.</p> <p><strong>Users</strong><br /> Only Fleet Managers</p>
20243M&U Passenger/Bag Flag01382MUOSDNewSubmitted: 01 October 2018<p><strong>Description</strong><br /> When 'Profiling' a FAST Reportable asset, fields capturing "Nbr of Passengers" and "Nbr of Bags" are mandatory and the data captured is not used.  And the definition for Nbr of Bags on the 'Help' screen is incorrect.</p> <p><strong>Recommended</strong><br /> Remove the mandatory flag from these fields until we work SCR 644/859 (Utilization by Other Means) to capture and use this data.  There is no workaround solution for this.</p> <p><strong>Mission Critical</strong><br /> Neither.</p> <p><strong>Benefits</strong><br /> Reduces time and number of 'clicks' in the total evolution.</p> <p><strong>Users</strong><br /> Only M&U users with role access to Maint Asset Master</p>
20242Equipment Pool ID Inc.01381MUOSDNewSubmitted: 01 October 2018<p><strong>Description</strong><br /> Current Equipment Pool Identifier construct is 2 unique alphanumeric characters which will not cover the over 400 EP required by Army Cadet Command and recruiters.</p> <p><strong>Recommended</strong><br /> Request increasing EP ID to 4 alphanumeric characters.</p> <p><strong>Mission Critical</strong><br /> Mission critical to obtain total asset visibility within MA</p> <p><strong>Benefits</strong><br /> Reduces time by allowing FM total visibility in one MA vice having to manager several MAs to meet the requirement of EP.</p> <p><strong>Users</strong><br /> Only affects Maintenance Activities with EP greater than 150 sites.</p>
20241NMC Status Date Field01380MUAF: VSCOSDoneSubmitted: 17 Sept 2018<p><strong>Description</strong><br /> Currently when updating from NMCM to NMCS or NMCS to NMCM the basic tab of Work Order defaults to the server time stamp to record the status change.  VSCOS currently has a need at times to back date this status change rather than real time server stamping. </p> <p><strong>Recommended</strong><br /> To give ability to back date the status change date field will need to be added to the NMC Basic tab.  "NMC Status Date", the field will be editable defaulting to server date time stamp, with validations against the NMC Tab of Work Order to ensure no status date conflicts exist and validate against NMC Begin date field and NMC End date field on Basic tab. </p> <p><strong>Mission Critical</strong><br /> Mandated to capture the time an asset actually was out of service not when the work-order was open.</p> <p><strong>Benefits</strong><br /> Gives users to update Work Orders that may have not have been updated in DPAS in "Real Time" as statuses changed. </p> <p><strong>Users</strong><br /> Yes</p> <p><strong>Completed – Release 6.3 – 21 December 2018</strong></p>
20240Turn line item red when other than A coded01379WarehouseAF: AFERMSDoneSubmitted: 20 Sept 2018<p><strong>Description</strong><br /> Need to be able to be able to tell which item is coded other than A inside a kit. Currently you have to expand every item or print off a DW-01 to see which item in the kit is coded other than A code. The amount of time clicking expansion arrows is more than excessive.</p> <p><strong>Recommended</strong><br /> Add ability to turn the line item in the SKO red if it is other than A coded. This will give the user a quick reference and allow a major time saving. See attached Story Board</p> <p><strong>Mission Critical</strong><br /> highly desired</p> <p><strong>Benefits</strong><br /> time savings, will be able to find item quicker and change out in a timely fashion.</p> <p><strong>Users</strong><br /> All</p> <p><strong>Completed – Release 7.1 – 26 July 2019</strong></p>
20239Add Additional Fields To Receive Screen01378EnterpriseSPECWARCOMDoneSubmitted: 8 AUG 18<p><strong>Description</strong><br /> When Receiving assets, the asset nomenclature (Item Desc) does not appear on Verified and Accept Grid</p> <p><strong>Recommended</strong><br /> Add Item Desc column to Verified Grid optional</p> <p><strong>Mission Critical</strong><br /> Mission Critical</p> <p><strong>Benefits</strong><br /> Reduces time and improves accuracy</p> <p><strong>Users</strong><br /> Affects all users within agency</p> <p><strong>Completed – Release 2021.1 – 5 February 2021</strong></p>
20238Daily FLIS Updates01377WarehouseSPECWARCOMDoneSubmitted: 8 AUG 18<p><strong>Description</strong><br /> WH does not always have the latest feed of FedLog, so when attempting to add an NSN, if the WH does not locate the NSN within its latest feed from FedLog, we are forced to enter the NSN as part number.</p> <p><strong>Recommended</strong><br /> Have real time updates pushed to FedLog, or do not mandate that when an NSN is selected, you are required to retrieve the NSN from WH's latest FedLog feed.</p> <p><strong>Mission Critical</strong><br /> Mission Critical</p> <p><strong>Benefits</strong><br /> Reduce time and improves accuracy</p> <p><strong>Users</strong><br /> Affects all users within agency</p> <p><strong>Completed – Release 7.1.2 – 30 Aug 2019</strong></p>
20237Display Min/Max Values01376WarehouseSPECWARCOMNewSubmitted: 8 AUG 18<p><strong>Description</strong><br /> Min Stock Qty and Max Stock Qty are not visible in the Inventory Update Manager Grid.</p> <p><strong>Recommended</strong><br /> Add Min Stock Qty and Max Stock Qty to the list of Grid Options/Columns for Inventory Update Manager</p> <p><strong>Mission Critical</strong><br /> Mission Critical - need a better to display min and max values for easy reordering</p> <p><strong>Benefits</strong><br /> Reduces time and improves accountability</p> <p><strong>Users</strong><br /> Affects all users within agency</p>
20236ICN Inquiry - Issued To Inquiry01375WarehouseSPECWARCOMDoneSubmitted: 8 AUG 18<p><strong>Description</strong><br /> Assets only show that it has been issued; users need to be able to identify where it was issued to and the name of the member attached to the issue</p> <p><strong>Recommended</strong><br /> For all serialized assets displayed within this query, add the following: the issue type as 'Individual' or 'Unit' and then identify the UIC it was issued to, then identify the member associated with the issue.</p> <p><strong>Mission Critical</strong><br /> Mission Critical - Needed for a one stop shop of inventory visibility</p> <p><strong>Benefits</strong><br /> Reduces time and improves accountability</p> <p><strong>Users</strong><br /> Affects all users within agency</p> <p><strong>Completed – Release 2021.1 – 5 February 2021</strong></p>
20235ICP - Multiple Stock Nbrs01374WarehouseSPECWARCOMNewSubmitted: 8 AUG 18<p><strong>Description</strong><br /> User is only allowed to enter one (1) RSA at time for a each stock number within the stock Item Catalog</p> <p><strong>Recommended</strong><br /> Allow more than one (1) RSA to be entered / selected when adding a stock number to the stock item catalog</p> <p><strong>Mission Critical</strong><br /> Mission Critical - The amount of time it takes to authorize the use of stock numbers for all 200 plus warehouses is extremely time consuming</p> <p><strong>Benefits</strong><br /> Reduces Time and allows the cataloging to move along efficiently and effectively.</p> <p><strong>Users</strong><br /> Affects all users within agency</p>
20234IntelliSense Stock Nbr field and Item Desc01373WarehouseSPECWARCOMNewSubmitted: 8 AUG 18<p><strong>Description</strong><br /> When conducting an Individual Issue, adding an item by stock number is required. The Stock Number field has the IntelliSense feature as well as the Browse feature. The IntelliSense feature only allows for the Stock Number to be queried if the Stock Number in known. Many of the users do not know the Stock Number or the Stock Number is not readily available; the users resort to the Browse feature for each item, which slows down the process. Many Stock Numbers contain the string of same numbers, which users are not able to distinguish between; this sends the user back to the Browse feature. </p> <p><strong>Recommended</strong><br /> Make the Stock Number IntelliSense field have the ability to produce options when user enters Stock Number or Item Description for an individual issue</p> <p><strong>Mission Critical</strong><br /> Mission Critical</p> <p><strong>Benefits</strong><br /> Reduces time</p> <p><strong>Users</strong><br /> Affects all users within agency</p>
20233Individual Issue Improvement01372WarehouseSPECWARCOMNewSubmitted: 8 AUG 18<p><strong>Description</strong><br /> When searching for the stock number to be issued, the search feature searches the entire LP Stock Number Catalog.</p> <p><strong>Recommended</strong><br /> Need the search feature within this process to only return stock numbers for which have O/H qty with the WH they are being issued from. (needs to include all processes and lock down to what stock item catalog has)</p> <p><strong>Mission Critical</strong><br /> Mission Critical - Need to cut down on the time to issue material when not using a Master Issue List</p> <p><strong>Benefits</strong><br /> Reduces time and improves accuracy</p> <p><strong>Users</strong><br /> Affects all users within agency</p>
20232Inventory Update Manager - Add Zone01371WarehouseSPECWARCOMNewSubmitted: 8 AUG 18<p><strong>Description</strong><br /> Zone to the list of Grid Options in the Inventory Update Manager</p> <p><strong>Recommended</strong><br /> Add Zone to the list of Grid Options/Columns in the Inventory Update Manager</p> <p><strong>Mission Critical</strong><br /> Mission Critical</p> <p><strong>Benefits</strong><br /> Better visibility</p> <p><strong>Users</strong><br /> Affects all users within agency</p>
20231Inventory Update Manager Grid - Last Inv Date01370EnterpriseSPECWARCOMNewSubmitted: 8 AUG 18<p><strong>Description</strong><br /> Last Inv Date is not available on the Inventory Update Manager Grid</p> <p><strong>Recommended</strong><br /> Add Last Inv Date to the list of Grid Options/Columns for Inventory Update Manager</p> <p><strong>Mission Critical</strong><br /> Mission Critical - Allows for one stop shop of inventory management</p> <p><strong>Benefits</strong><br /> Reduces time</p> <p><strong>Users</strong><br /> Affects all users within agency</p>
20230Allow 'Bulk' assets with a '0' O/H qty to remain displayed on active inventory01369WarehouseSPECWARCOMNewSubmitted: 8 AUG 18<p><strong>Description</strong><br /> Allow 'Bulk' assets with a '0' O/H qty to remain displayed on active inventory. Allow 'Bulk' assets with a '0' O/H qty to remain displayed on active inventory</p> <p><strong>Recommended</strong><br /> Create a checkable box on the Replenishment Info tab in the Catalog Mgmt - Stock Item - Edit Stock Items pop-up window. The zero footprint should be a selectable option and not be automatically applied to all items.  If stock item becomes obsolete or unit no longer carries item it can be deselected, removing the zero footprint from inventory</p> <p><strong>Mission Critical</strong><br /> Mission Critical - Users need to see what items are at 0 O/H qty</p> <p><strong>Benefits</strong><br /> Allows for forecasting needs</p> <p><strong>Users</strong><br /> Affects all users within agency</p>
20229Limit Physical Inv Visibility01368WarehouseSPECWARCOMNewSubmitted: 8 AUG 18<p><strong>Description</strong><br /> Users have the ability to create, view, edit, cancel, and conduct a Physical Inventory for a Secure Commodity they do not have access to</p> <p><strong>Recommended</strong><br /> Limit Physical Inventory visibility. Unless user has access to that specific Secure Commodity; a user should NOT have the ability to create, view, edit, cancel, and conduct a physical inventory for a Secure Commodity he does NOT have access to</p> <p><strong>Mission Critical</strong><br /> Mission Critical</p> <p><strong>Benefits</strong><br /> Improves accountability</p> <p><strong>Users</strong><br /> Affects all users within agency</p>
20228Location Archive / Member Profile01367WarehouseSPECWARCOMNewSubmitted: 8 AUG 18<p><strong>Description</strong><br /> Users do NOT have the ability to remove a location/member profile they no longer have a need for</p> <p><strong>Recommended</strong><br /> Provide users the ability to archive or deactivate a warehouse location/member profile no longer in use or deemed unnecessary. Have ability to reactivate as well</p> <p><strong>Mission Critical</strong><br /> Mission Critical - Need for basic warehouse and personnel maintenance</p> <p><strong>Benefits</strong><br /> Allows for better inventory management</p> <p><strong>Users</strong><br /> Affects all users within agency</p>
20227Master Issue List Limited Access01366WarehouseSPECWARCOMIn ProgressSubmitted: 8 AUG 18<p><strong>Description</strong><br /> Each warehouse has visibility, as well as the ability to edit or delete everyone else's Master Issue List</p> <p><strong>Recommended</strong><br /> Limit visibility and edit/delete functions to the owning warehouse who originally created the Master Issue List</p> <p><strong>Mission Critical</strong><br /> Mission Critical - Need prevent people from deleting and editing MIL's that do not belong to them.</p> <p><strong>Benefits</strong><br /> Improves accountability</p> <p><strong>Users</strong><br /> Affects all users within agency</p> <p><strong>Partially Completed - Release 2021.3 - 10 Sept 2021</strong></p>
20226Printing Multiple DD1348s01365WarehouseSPECWARCOMIn ProgressSubmitted: 8 AUG 18<p><strong>Description</strong><br /> Users are only allowed to print one (1) DD1348 at a time in the Disposition function and all other processes.</p> <p><strong>Recommended</strong><br /> For all assets that were disposed of within a container, WM should have the function that allows the user to print out multiple DD1348's in one click. The same way the user is allowed to dispose of assets in a container in one click.</p> <p><strong>Mission Critical</strong><br /> Mission Critical - Need to print all 1348 associated with a single disposal action to save time</p> <p><strong>Benefits</strong><br /> Reduces time</p> <p><strong>Users</strong><br /> Affects all users within agency</p> <p><strong>Partially Completed - Release 2021.3 - 10 Sept 2021</strong></p>
20225Stock Nbr Update01364EnterpriseSPECWARCOMNewSubmitted: 8 AUG 18<p><strong>Description</strong><br /> When editing a Stock Nbr, the following fields are locked and unable to be edited; Stock Number, Type Asset Code, & ACC</p> <p><strong>Recommended</strong><br /> Allow users with access to the Stock Number Catalog the ability to update a stock number, Type Asset Code, & ACC</p> <p><strong>Mission Critical</strong><br /> Mission Critical - Stock numbers are often updated and need to be changed by local catalog team instead of sending help ticket to Leidos</p> <p><strong>Benefits</strong><br /> Reduces time</p> <p><strong>Users</strong><br /> Affects all users within agency</p>
20224Student Class Name01363WarehouseSPECWARCOMDoneSubmitted: 8 AUG 18<p><strong>Description</strong><br /> Need the ability to group students together by their Class Name.</p> <p><strong>Recommended</strong><br /> Add 'CLASS NAME'  to Member Profile, to Sub-Grid, and Member Import template, but not restricted to year</p> <p><strong>Mission Critical</strong><br /> Mission Critical</p> <p><strong>Benefits</strong><br /> Improves accuracy and accountability</p> <p><strong>Users</strong><br /> Affects all users within agency</p> <p><strong>Completed – Release 7.1 – 26 July 2019</strong></p>
20223View Users' Assigned Secure Commodities01362WarehouseSPECWARCOMNewSubmitted: 8 AUG 18<p><strong>Description</strong><br /> Ability to view what Secure Commodities warehouse users have been assigned. (No front end capability and Leidos has said this is something they can't pull for us)</p> <p><strong>Recommended</strong><br /> Ability to view what Secure Commodities warehouse users have been assigned. (No front end capability and Leidos has said this is something they can't pull for us)</p> <p><strong>Mission Critical</strong><br /> Mission Critical - Need to quickly determine what users have access to what secure commodities during command audits and inspection without needing to ping Leidos every time.</p> <p><strong>Benefits</strong><br /> Reduces time and improves accountability</p> <p><strong>Users</strong><br /> Affects all users within agency</p>
202221149 Improvements01361WarehouseSPECWARCOMNewSubmitted: 8 AUG 18<p><strong>Description</strong><br /> Many critical fields within the 1149 are blank after a Warehouse Issue or Transfer is completed.</p> <p><strong>Recommended</strong><br /> Populate the 1149 based off the examples provided by NSW</p> <p><strong>Mission Critical</strong><br /> Mission Critical</p> <p><strong>Benefits</strong><br /> Reduces time and improves accountability/financial reporting</p> <p><strong>Users</strong><br /> Affects all users within agency</p>
20221CIP Improvements01360PADISANewSubmitted: 9/12/2018<p><strong>Description</strong><br /> Currently DPAS requires CIP projects to be defined as supporting the creation of an Asset or an Improvement.  DISA has projects where materiel is purchased / costs are accumulated that provide support to both Assets and Improvement to an Assets, and in some instances to provide Ancillary Costs to existing assets.  DPAS should provide for a single project to be used to substantiate an Asset, Improvement to an existing Asset, and Ancillary Costs.  <br />The other improvement to CIP Project is to generate Accounting Events supporting the change in Lines of Accounting between the Project and the item being created.  Today, the relieving of CIP is based upon the fund source (New Procurement or Transfer).  When New Procurement, the accounting transactions created will always be "X819", "M", Dollar Amount, when relieving it.  DPAS should compare the Project's Fund Cd/ ASN to that of the asset being created.  When the same, then an X819 "M" for the dollar amount would be appropriate.  If they are not the same, then the relieving of the CIP of the dollars should be treated as a Transfer Out "X817" with the new Asset, Improvement or Ancillary Cost  receipt being treated as a Transfer In "X815".</p> <p><strong>Recommended</strong><br /> The recommended CIP improvements will enable DISA to utilize the CIP Module as it was intended.  Today, CIP projects created by DISA to track the costs being incurred must be reversed when the item is completed (Asset, Improvement, Ancillary Cost), then manually established.   Financially a transfer of funding between General Fund and Working Capital fund monies as assets must be accounted for correctly. </p> <p><strong>Mission Critical</strong><br /> Financial audits compel DISA to review all its business practices.  The more automation can be applied to these business practices, the greater chance compliance will be maintained.  These changes will enable DISA to create an asset, improvement, ancillary cost directly from within the CIP modules which ensure the costs of the item is maintained throughout its life should unknown costs be posted to the CIP account after the item has been booked.</p> <p><strong>Benefits</strong><br /> Improves accuracy of financial reporting and would allow DISA to move to an automated interface for General Fund Capital assets.</p> <p><strong>Users</strong><br /> This change would only affect accounting/property personnel within the Capital Asset Management team - will not affect other property personnel.</p>
20220Add RPUID to Location Table01359PANavyDoneSubmitted: September 12, 2018<p><strong>Description</strong><br /> There is no method available to identify the installation, city and state an asset is located.</p> <p><strong>Recommended</strong><br /> Add the RPUID to the Location process in the Property Accountability module.  Also add the installation, facility, city, state and any other pertinent data from the Real Property record to the Asset Inquiry.</p> <p><strong>Mission Critical</strong><br /> The audit community has asked for the data by city and state.</p> <p><strong>Benefits</strong><br /> Makes locating an asset simpler for personnel that are not involved in the daily management of the assets.</p> <p><strong>Users</strong><br /> All</p> <p><strong>Completed – Release 7.0 – 20 April 2019</strong></p>
20219LP and Warehouse Catalog01341EnterpriseAF: VSCOSNewSubmitted: 7 Sept 2018<p><strong>Description</strong><br /> For the AF 85-90% of vehicle parts are purchased commercially off-the-shelf. DLA/USAF supply is scarcely used. Warehouse does not allow for (commercial) similar/duplicate part numbers from different manufacturers, which poses a challenge for 303 warehouses globally to operate from one Logistics Program (LP) catalog. It is very time consuming loading single part numbers with 26 data points.</p> <p><strong>Recommended</strong><br /> Need capability to load duplicate (commercial) part numbers with different descriptions in the LP. Eliminate unnecessary data points when loading a part number. When loading NSN or part number from LP to warehouse catalog, disassociate selected number from LP for warehouse to manage as needed.  </p> <p><strong>Mission Critical</strong><br /> It is mission critical and is mandated</p> <p><strong>Benefits</strong><br /> Process will expand parts catalog capability and allow future changes as new models of vehicles & vehicular equipment are introduced to the USAF vehicle fleet.</p> <p><strong>Users</strong><br /> This option would benefit all M/U and Warehouse users.</p>
20218Zone Option for ICN Inventory01337WarehouseAF: VSCOSNewSubmitted: 7 Sept 2018<p><strong>Description</strong><br /> Vehicle maintenance personnel are required to pull inquiries that display items in multiple locations but within the same zone. Personnel with the 9090 role require access to this information and the ICN Inventory currently doesn't have an option to create an inquiry by zone.</p> <p><strong>Recommended</strong><br /> Add an option to pull an ICN Inventory by zone.</p> <p><strong>Mission Critical</strong><br /> Not mission critical or mandated.</p> <p><strong>Benefits</strong><br /> This change will allow all personnel to pull inquiries for daily functions that are organized by zones.</p> <p><strong>Users</strong><br /> This change will have a beneficial impact on all Warehouse users since it will enable them to access inventory listings for functions and processes that are organized by zones.</p>
20217SKO Build and Inventory With SKO Catalog Options01334WarehouseAF: VSCOSNewSubmitted: 7 Sept 2018 AND 05 October 2018<p><strong>Description</strong><br /> Warehouse needs SKO listing and inventory/inspection improvement to be IAW AFI 24-302 requirements and AF Vehicle Management (VM) common tool accountability and management practice. The SKO catalog list and inspection list must be the same. <br /><strong>ALSO</strong> <br />An addition to SCR 1334. Along with using toolboxes/Individual Tool Kit (ITK)/Composite Tool kit (CTK), the Vehicle Management (VM) community also uses containers/Mobility Spares Readiness Package(MRSP) and pallets for mobility purposes. Having multiple SKO catalog options would be ideal for VM facilities and other DoD DPAS users.</p> <p><strong>Recommended</strong><br /> Modify SKO catalog.  Units should have the ability to build toolbox or kits (SKO) with display order and drawer location.  See Attachment 3 (DW Form 01A) for recommended document appearance. <br /><strong>ALSO</strong> <br />We recommend removing current SKO option and adding the capabilities to select different types of SKO catalogs: ITK/CTK, MSRP and Pallet. Upon selecting add in the SKO Catalog screen, the system should ask which type of catalog the user is trying to create. All three options (ITK/CTK, MSRP and Pallet) will have the option to group items by compartments/drawers and still have the option for display order.</p> <p><strong>Mission Critical</strong><br /> It is mission critical and is mandated. <br /><strong>ALSO</strong> <br />IAW 24-302 5.37.6. Maintenance team leads or their designees perform and document accountability procedures for ITK/CTKs or tool cribs in accordance with local Vehicle Management Operation Procedures (VMOPs), or on a daily basis, to ensure accountability of assigned tools and to prevent Foreign Object Damage (FOD). (T-1). Written inventories are accomplished annually by Materiel Control, jointly with the technician. <br />5.37.15 Powered hand tools may be issued to CTKs, tool cribs or ITKs. Ensure they are accurately accounted for due to their high replacement cost.<br />5.39. Materiel Control sub-receipts ITKs to the technicians using itemized inventory listings.</p> <p><strong>Benefits</strong><br /> VM operations have SKOs with over 500 tools.  Having SKOs with display order and drawer location enables members/personnel to easily locate and inspect tools.  <br /><strong>ALSO</strong> <br />The option to have multiple SKO programs to catalog parts and tools for ITK/CTKs, MSRPs and Pallets will allow better accountability management and make the inventory process more efficient.</p> <p><strong>Users</strong><br /> This option would benefit all Warehouse users. See attached document for visual explanation <br /><strong>ALSO</strong><br />Not only will the Air Force component benefit from this SCR but all DoD and Federal services using DPAS and the SKO function. The capability will allow better tool, parts, equipment management/accountability and increase inventory efficiency.</p>
20216Update Part Costing to Actual Asset Cost (not Catalog Cost)01332EnterpriseAF: VSCOSNewSubmitted: 7 Sept 2018<p><strong>Description</strong><br /> Warehouse capability is needed to update receive/accept process to be IAW AFI 24-302, chapter 5 requirements. Parts receipt and/or Form DD1348 costs must be loaded to document/account for funds charged to vehicles.  Actual part cost also needs to reflect in "Unit Cost" field in M&U when Document Status reflects "Issued".  Currently, this field reflects the catalog cost.</p> <p><strong>Recommended</strong><br /> Modify Warehouse, Materiel Mgmt, Receiving, Receive and Accept process.  Allow for price modification from parts receipt and/or Form DD1348 costs to reflect actual cost not LP list price.  Actual asset cost also needs to reflect in "Unit Cost" field in M&U when Document Status reflects "Issued".</p> <p><strong>Mission Critical</strong><br /> It is mission critical and is mandated per DoD 4500.36, Chapter 2b "The cost associated with this method of NTV support includes these cost elements...Direct and indirect costs associated with the operation and maintenance of the NTV". Accuracy of costing inputs sustainment budget and is calculated in FAST Cost per Mile, our End of Life and Prioritization Models.</p> <p><strong>Benefits</strong><br /> Having actual part cost gives accurate accounting of items purchased and allows accurate reporting of operation and maintenance costs associated with each asset.</p> <p><strong>Users</strong><br /> This option would benefit all Warehouse users. See hatched document for visual explanation</p>
20215Deferred Parts process M/U & Warehouse01331EnterpriseAF: VSCOSDoneSubmitted: 7 Sept 2018<p><strong>Description</strong><br /> M&U W/O/sub-W/O parts request tab needs to have capability to indicate and process deferred parts request, also accounting status for partial or completed back-ordered parts received data from Warehouse IAW AFI 24-302 Section 5E. (Addition to <a href="index.php/support/system-change-request/details/4/19988/priority-levels-for-mu-and-warehouse-orders">SCR 01162</a>)</p> <p><strong>Recommended</strong><br /> Create deferred maintenance W/O pool that does not count toward assets NMC time. Allow W/O to be reopened at later date for specific deferred (back-ordered) parts to be installed. (see attachment below).</p> <p><strong>Mission Critical</strong><br /> It is mission critical and is mandated</p> <p><strong>Benefits</strong><br /> Process will allow assets to be FMC to users while allowing for the processing of non-safety parts orders to be filled at a feasibly later time.</p> <p><strong>Users</strong><br /> This option would benefit all M/U and Warehouse users.</p> <p><strong>Completed – Release 7.1 – 26 July 2019</strong></p>
20214Maint Issue Open Action Update01338EnterpriseAF: VSCOSNewSubmitted: 7 Sept 2018<p><strong>Description</strong><br /> Material Control Officers usually work in different sections than personnel who request items from the M&U module and they need to be aware of any Maintenance Issue requests.</p> <p><strong>Recommended</strong><br /> Maintenance Issue Request from M&U should display in the Open Warehouse Actions and Message of the Day Dashboard.</p> <p><strong>Mission Critical</strong><br /> Materiel Control section is mandated per AFI 24-302 to "Initiate, monitor and follow up (as needed/required) on part requests".  Initiating this change will highlight pending parts requests.</p> <p><strong>Benefits</strong><br /> Displaying these requests in the open actions and message of the day dashboard will raise awareness and accelerate the purchase process.</p> <p><strong>Users</strong><br /> This change will have a beneficial impact on all users that purchase and issue parts along with personnel that request the parts.</p>
20213Parts Request Process for Items not Currently Catalogued01329EnterpriseAF: VSCOSNewSubmitted: 7 Sept 2018<p><strong>Description</strong><br /> M/U does not allow for part numbers to be requested without being loaded to Logistics Program (LP) and warehouse, which poses a challenge for technicians to request parts using the M/U part tab. Technicians would need to manually send required 26 data points to the Materiel Control Officer to load part numbers to LP and warehouse to allow technician to go back to M/U part request.</p> <p><strong>Recommended</strong><br /> Minimize the amount of information needed from the technician to get part on demand. Need capability to request part numbers using M/U and will transfer part information to Materiel Control Officer via warehouse module to load to catalog; in order to conduct a more fluid ordering process. Also, allow tab to transfer remarks; stating recommended source of supply or vendor.</p> <p><strong>Mission Critical</strong><br /> It is mission critical and is mandated</p> <p><strong>Benefits</strong><br /> Process will expand parts catalog capability and allow future changes as new models of vehicles & vehicular equipment are introduced to the USAF vehicle fleet.</p> <p><strong>Users</strong><br /> This option would benefit all M/U and Warehouse users.</p>
20212GSA/DLA Mass Mileage Upload01342MUAF: VSCOSNewSubmitted: 7 Sept 2018<p><strong>Description</strong><br /> Currently, mass mileage can be uploaded via GSA Fleet file upload and DLA Fuel upload.  GSA upload will update fuel usage as well as mileage.  DLA will update fuel but no miles;  however the odometer field is still mandatory for the system to accept the file.  The issue is both GSA and DLA mileage inputs by users at the pumps are mostly incorrect (i.e. people make up numbers or use the tenth of a mile on the odometer; 1600.9 miles becomes 16009).<br />Our Fleet Management and Analysis section needs to be able to collect and verify all mileage updates before loading into DPAS. </p> <p><strong>Recommended</strong><br /> Separate the mileage mandate from the current GSA/DLA fuel upload capability.  Create a bulk upload template for both GSA an DLA fuel uploads.  For ease of upload, suggest utilizing current GSA bulk mileage upload spreadsheet that exists in the GSA Fleet Drive-thru website.  Create a similar type mass upload sheet for DLA mileage uploads.</p> <p><strong>Mission Critical</strong><br /> This is a mission critical change.  Incorrect mileage can send scheduled maintenance dates well out of range as well as affect both vehicle End of Life and Priority Buy models. Both are key to the Air Force vehicle fleet replacement placement. </p> <p><strong>Benefits</strong><br /> This feature will reduce the time it takes to input hundreds of mileage updates one by one as well as increase the accuracy of the data being entered. Our fleet has 83K assets, to have our FMIS be able improve fuel reporting efficiency and accuracy is vital to day to day mission success.</p> <p><strong>Users</strong><br /> All Air Force Fleet Managers/Maintenance controllers and Material specialists utilize this information for day to day fleet management purposes.  </p>
20211Auto Save every 10 min minutes (similar to Word Docs)01340EnterpriseAF: VSCOSNewSubmitted: 7 Sept 2018<p><strong>Description</strong><br /> Currently, there is not a way for a user to back up data that has been inputted into DPAS M&U and are still trying to complete the transaction, before their 15 minute time is up. So any data inputted before clicking update is lost, and is very time consuming to re-enter. Especially, if the Work Order has numerous Sub Work Orders.</p> <p><strong>Recommended</strong><br /> The ability to have DPAS M&U auto save (like Word Docs) every 10 min would be a great add on to the program. This will ensure that users have time to input information or make updates without worrying that they don't have time, and make a mistake or if they get called away mid-transaction. Also, the fleet management personnel might have to stop mid way during the profiling, utilization update or work order process to retrieve additional information.</p> <p><strong>Mission Critical</strong><br /> This is critical, this will give adequate time for the user to input data accurately and without concern of losing information already inputted. Currently, the inability to save data is not user friendly to daily operations.</p> <p><strong>Benefits</strong><br /> This would benefit users (having the security of not losing data); increasing productivity and maintenance leadership getting the most accurate and up to date maintenance information of assets in maintenance in a timely manner.</p> <p><strong>Users</strong><br /> This SCR will affect the entire AF Agency, all fleet managers/maintenance controllers utilize up to date information for day to day fleet management purposes.  </p>
20210Work Plan Type Cd Correction and/or Addition01336MUAF: VSCOSNewSubmitted: 7 Sept 2018<p><strong>Description</strong><br /> DPAS will not allow the use of Work Plan Type Cd "INSP" more than once on a work order.  If a second sub work order is created with "INSP" an error message displays "2-Invalid entry: there is more than one INSP sub work order.  A work order can have at most one INSP sub work order"</p> <p><strong>Recommended</strong><br /> Allow multiple inspections to be inputted on more than one sub work order and/or create specific work plan type codes for "INCM/Incoming" and "OUTG/Outgoing" inspections.</p> <p><strong>Mission Critical</strong><br /> This is mission critical as many inspections such as incoming, outgoing quality control and visual inspections are mandated per AFI 24-302 and T.O. 36-1-191.</p> <p><strong>Benefits</strong><br /> Benefits of implementing this change will allow more accurate maintenance action classification reporting and fleet analysis.</p> <p><strong>Users</strong><br /> All Air Force fleet managers, maintenance controllers and material control specialists utilize this information for day to day fleet management purposes.  </p>
20209Combining System Generated Work orders01335MUAF: VSCOSNewSubmitted: 7 Sept 2018<p><strong>Description</strong><br /> Currently, when an asset is due scheduled maintenance/inspection, a system generated work order will open up for each individual maintenance/inspection due.  As it stands right now, work plan(s) can be combined to one work order and the unneeded work order voided.  However, the voided work order still self generated as "due" the next day.</p> <p><strong>Recommended</strong><br /> Add feature to work order that will allow other system generated work orders to be combined and prevent another instance of the same maintenance/inspection from self generating again the next day.</p> <p><strong>Mission Critical</strong><br /> Yes.  The current configuration allows several work orders be open for the same asset leaving the open work orders screen clogged full of unnecessary "open" work orders and makes it difficult for vehicle managers to get an informed snap shot of what is currently open within the shop.</p> <p><strong>Benefits</strong><br /> The benefits of implementing this change will reduce the "clutter" within the open work order screen/open actions screen and provide a clearer site picture of what assets are actually down for maintenance.</p> <p><strong>Users</strong><br /> All fleet managers, maintenance controllers and materiel specialists utilize this information for day to day fleet management purposes.  </p>
20208Permanently attach Mx records for life of asset01333MUAF: VSCOSNewSubmitted: 7 Sept 2018<p><strong>Description</strong><br /> Currently, when an asset is transferred from one UIC to another, all maintenance history/records is removed and does not follow the asset. </p> <p><strong>Recommended</strong><br /> Ensure all historical maintenance records and attachments are electronically attached to the asset for its entire life cycle. Have MU mimic PA functions for records updates and attachment management.</p> <p><strong>Mission Critical</strong><br /> Very mission critical.  If the entire assets maintenance history is not available, it is difficult to identify maintenance trends and recurring issues. It also hinders researching previous Service Bulletins, Manufacturer's Warranties, One Time Inspections and Time Compliance Technical Orders that have been completed which could lead to potential safety issues. </p> <p><strong>Benefits</strong><br /> Implementing this solution will ensure all historical data is available to maintenance managers for the life of the asset; in order for trends and safety issues to be easily identified. </p> <p><strong>Users</strong><br /> All Air Force Fleet Managers/Maintenance controllers and Material specialists utilize this information for day to day fleet management purposes.  </p>
20207Nuclear, Reimbursable, Mission Critical Indicator Reflect on Basic Work Order01330MUAF: VSCOSNewSubmitted: 7 Sept 2018<p><strong>Description</strong><br /> Currently, there is no way to identify that an asset is nuclear certified, reimbursable or mission critical when opening a work order. Fleet analysts and mechanics need a simple way to distinguish assets that are identified as nuclear certified, reimbursable or mission critical to properly direct and perform maintenance actions. </p> <p><strong>Recommended</strong><br /> Add three fields with drop down selections on the Maint Asset screen. The fields can be located on the Basic or Vehicle Characteristics tab.  The Field names and drop down selections will simply have the options Nuc Cd "N" for nuclear, Remb/Refd "4" for reimbursable/5 for refundable" and Msn Crt "C" for mission critical.  Fields will be blank or N/A for the conditions that do now apply.  The field name and codes "N", "4 or 5" and "C" will reflect on the basic work order tab when opening a work order and the technician work order when printed. See attachment which details basic requirement. Additionally, all fields (to include cost centers) need to be easily identifiable when pulling a Maint Asset inquiry or a work order/sub work order inquiry. </p> <p><strong>Mission Critical</strong><br /> Critical.  It is imperative that a technician know if a vehicle is certified to handle nuclear cargo or not.  Nuclear certified assets have additional rules that governs maintenance; requiring the technician an easily identifiable indicator on the work order to stay in compliance with AFI 63-125, Nuclear Certification Program.  Furthermore, it is imperative that Vehicle Management have an easily identifiable indicator and inquiry that an asset is refundable or reimbursable in order to recoup sustainment funds from an outside organization monthly as well as the ability to easily identify mission critical assets.</p> <p><strong>Benefits</strong><br /> Benefits of implementing this change includes saving research time when opening a work order, potential of performing maintenance improperly on a vehicle and decertifying it's nuclear certified status.  It will also, save time trying to identify refundable/reimbursable assets as well as improve accuracy of financial reporting per AFI 24-302, para 4.20 "Ensure Reimbursable units are coded correctly and perform follow up actions for financial recoupment."</p> <p><strong>Users</strong><br /> All Air Force Fleet Managers/Maintenance controllers and Material specialists utilize this information for day to day fleet management purposes.  </p>
20206Calculate and Display Mission Capable Rate (percentage)01328MUAF: VSCOSDoneSubmitted: 7 Sept 2018<p><strong>Description</strong><br /> Currently, there is no feature within DPAS that displays daily or monthly cumulative Mission Capable (MC) rate percent. </p> <p><strong>Recommended</strong><br /> Add daily MC rate to the DPAS Maint and Utilization Home Page and create a report that will display monthly cumulative MC rate. (NMCM+NMCS hours divided by available hours - 100 = MC%).  Calculation does not take into account any assets marked "NMC: NO" or non-accountable assets.</p> <p><strong>Mission Critical</strong><br /> This is mission critical and mandated.  Senior leaders as well as vehicle fleet managers utilize the MC rate as a snap shot of the overall health of the vehicle fleet.  MC rate is also mandated per DoDM 4500.36.</p> <p><strong>Benefits</strong><br /> The benefit of implementing this solution will improve maintenance leadership's ability to have an accurate and up to the minute sight picture of the health of the vehicle fleet and mission readiness. Air Force non tactical vehicles are also included in our warfighting capabilities (base security, runway repair, aircraft supporting, etc.) as a force multiplier. </p> <p><strong>Users</strong><br /> All Air Force Fleet Managers/Maintenance controllers and Material specialists utilize this information for day to day fleet management purposes.  </p> <p><strong>Completed – Release 2020.1 – 6 March 2020</strong></p>
20205Lock Est Labor Hours field to a mandatory field and add error indicator01356MUAF: VSCOSNewSubmitted: 5 Sept 2018<p><strong>Description</strong><br /> Currently, there is not a way to ensure Air Force M&U users input Estimated Labor Hours on Sub Work Orders. Estimated labor is a mandatory input for our user, currently the system allows users to by pass this field. This is necessary as part of our indirect costing formula and a FMIS requirement per GSA Bulletin FMR B-15, September 21, 2007, on identifying, collecting and analyzing motor vehicle data with respect to the costs-including indirect costs-incurred for the operation, maintenance. acquisition and disposition of motor vehicles.</p> <p><strong>Recommended</strong><br /> 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 field and a message needs to pop up when there is not a number in the Est Labor Hour field on this.</p> <p><strong>Mission Critical</strong><br /> This is critical.  Enterprise fleet managers count on viewing this information to be able to make informed decisions to manage Air Force fleets around the globe as well as meet GSA reporting requirements.</p> <p><strong>Benefits</strong><br /> This would benefit Air Force leadership by getting the most accurate and up to date maintenance information and meeting GSA Bulleting FMR B-15 for all federal assets.</p> <p><strong>Users</strong><br /> This SCR will affect all DPAS M&U users utilizing this information for day to day fleet management purposes.</p>
20204Add Edit of POC to Warehouse Technician Role01355WarehouseAF: AFERMSNewSubmitted: 4 sept 2018<p><strong>Description</strong><br /> Warehouse Technicians need to be able to Edit the Warehouse POC information.</p> <p><strong>Recommended</strong><br /> (see slideshow) Under Master Data Mgmt--Warehouse allow Warehouse Technicians the ability to Edit only the Warehouse POC information. Do Not allow them to edit any other data in Master Data Mgmt.</p> <p><strong>Mission Critical</strong><br /> highly desired</p> <p><strong>Benefits</strong><br /> time savings and data accuracy.</p> <p><strong>Users</strong><br /> All</p>
20203Inspection against Personnel for PEs01354WarehouseAF: AFERMSNewSubmitted: 4 sept 2018<p><strong>Description</strong><br /> Need to be able to do an inspection against a specific personnel.</p> <p><strong>Recommended</strong><br /> Add ability to inspect a specific personnel, we need to have a way to document Personnel Evaluations done by our QA. These inspections need to have the same process as other QA inspections and need to generate on the QA/QC reports when QA check box is selected.</p> <p><strong>Mission Critical</strong><br /> highly desired</p> <p><strong>Benefits</strong><br /> time savings and data accuracy.</p> <p><strong>Users</strong><br /> All</p>
20202Add Grid Option to Kit-Serial Kit Update Pop-ups01353WarehouseAF: AFERMSIn ProgressSubmitted: 4 sept 2018<p><strong>Description</strong><br /> Need to be able to see Shelf Life Expiration Date on the Grid in Kit Update and Serial Kit Update.</p> <p><strong>Recommended</strong><br /> Add Shelf Life Expiration Date to the Grid Options for Kit Update screens and Serial Kit Update screens.  Have it work the same way that Service Life Expiration Date works now, where if it has one it shows as a default on the Grid automatically.</p> <p><strong>Mission Critical</strong><br /> highly desired</p> <p><strong>Benefits</strong><br /> time savings and data accuracy.</p> <p><strong>Users</strong><br /> All</p> <p><strong>Partially Completed - Release 2021.3 - 10 Sept 2021</strong></p>
20201Next Inspection Dt01352WarehouseAF: AFERMSNewSubmitted: 4 sept 2018<p><strong>Description</strong><br /> Inspection allows users to put the next inspection date past component expiration dates.</p> <p><strong>Recommended</strong><br /> When a component is expiring before the normal auto populated next inspection date have it auto populate to the first component expiration date(including shelf and service life expirations) and grey out all dates past that, so they can't force the next inspection date.  If no components expire prior to the normal next inspection date, auto populate to the normal next inspection date. Also, give a note telling the user which component expires prior to the full next inspection date. (see powerpoint)</p> <p><strong>Mission Critical</strong><br /> highly desired</p> <p><strong>Benefits</strong><br /> time savings and data accuracy.</p> <p><strong>Users</strong><br /> All</p>
20200Add Search Criteria to ICN Inventory01351WarehouseAF: AFERMSIn ProgressSubmitted: 4 sept 2018<p><strong>Description</strong><br /> Need to add search criteria under Inquiries.</p> <p><strong>Recommended</strong><br /> Under Inquiries--Inventory--ICN Inventory Add the following to Search Criteria (do not require full number): Mfr Contract Nbr and Mfr Lot Nbr.</p> <p><strong>Mission Critical</strong><br /> highly desired</p> <p><strong>Benefits</strong><br /> time savings and data accuracy.</p> <p><strong>Users</strong><br /> All</p> <p><strong>Partially Completed - Release 2021.3 - 10 Sept 2021</strong></p>
20199QA-QC Reports01350WarehouseAF: AFERMSDoneSubmitted: 4 sept 2018<p><strong>Description</strong><br /> All QA/QC Reports pull four to six different reports when 'All" is selected for sort by.  They are not exported in a way that allows the user to easily sort further. They also should be showing sort by data in the search parameters on the view reports screen. QA/QC Totals reports are reflecting discrepancies as QCs, when they should be reflecting just the number of QC inspections for that number. This report needs to have a sort by option for the stock number.</p> <p><strong>Recommended</strong><br /> (See powerpoint for examples) Suggest removing the 'All' option for sort by to eliminate pull mult reports.  Make all reports use separate columns for all data, so users can sort further without accidentally losing data. Show sort by data in the search parameters drop down on the view reports screen.  Have QA/QC Totals report pull how many QC inspections were done, do not base off of discrepancy count. Add Stock Number sort option for the QA/QC Totals report.</p> <p><strong>Mission Critical</strong><br /> highly desired</p> <p><strong>Benefits</strong><br /> time savings and data accuracy.</p> <p><strong>Users</strong><br /> All</p> <p><strong>Completed – Release 7.2.00 – 8 November 2019</strong></p>
20198Physical Inventory tethered scan ability01349WarehouseAF: AFERMSDoneSubmitted: 1 Sept 2018<p><strong>Description</strong><br /> No ability to perform a basic Physical inventory with tethered scanner</p> <p><strong>Recommended</strong><br /> Add  scan block that can read either serial number or ICN as is done in the individual issue process. (see Power Point for examples)</p> <p><strong>Mission Critical</strong><br /> Critical, was explained that the system was a warehousing system and can't use the basic features that program was designed for</p> <p><strong>Benefits</strong><br /> time savings and data accuracy.</p> <p><strong>Users</strong><br /> All</p> <p><strong>Completed – Release 7.1 – 26 July 2019</strong></p>
20197SNAP-IT Association01348PAOSDNewSubmitted: 30 August 2018<p><strong>Description</strong><br /> Identifying the SNAP-IT within the Manufacturer AUD does not allow for multiple manufacture assignment to one stock number.  If SNAP-IT is assigned, no other manufacturer can be assigned forcing the creating of a new stock number for possibly the same piece of software.</p> <p><strong>Recommended</strong><br /> Move the SNAP-IT association to the asset level.  Possible location for SNAP-IT association may be Asset Receiving > Catalog or Asset Receiving > Asset Entry.</p> <p><strong>Mission Critical</strong><br /> The mandate is to associate the SNAP- IT to the asset accountable record.</p> <p><strong>Benefits</strong><br /> Allows multiple Manufacturers to be added to one NSN/MCN which reduces time and the number of NSN/MCNs to a catalog.</p> <p><strong>Users</strong><br /> Only users with access to Manufacturer AUD</p>
20196Software Name Creation01347PAOSDNewSubmitted: 30 August 2018<p><strong>Description</strong><br /> For GOTS and Modified COTS SW Mgmt Types, the SW name is usually unconventional or internally named.  Users would constantly seek to update the SW Name table and this would be commingled with COTS.</p> <p><strong>Recommended</strong><br /> Move the Software Name function to Asset Receiving > Asset Entry tab so the SW Name is on the asset record.  Also, if SW Mgmt Type is GOTS or Modified COTS, allow SW Name to be Free Text to keep from updating table constantly.</p> <p><strong>Mission Critical</strong><br /> Critical to user for inventory identification.</p> <p><strong>Benefits</strong><br /> Improves the accuracy and management of IUS during receipt, validation and disposition.</p> <p><strong>Users</strong><br /> APO, PA Receiving</p>
20195Serialized SKO01346WarehouseArmy: USASOCNewSubmitted: 30 Aug 2018<p><strong>Description</strong><br /> When managed and unmanaged kit items are assembled in Warehouse module, there is no indication of the kit's value besides the FLIS value assigned.  The final products' unit price may exceed the capitalization threshold, causing the OM&S to become financially reportable as general equipment.  Unclear how the end-items' unit price will be derived and reported (via Materiel Management module).  Need DW Form 08 (or similar report) to show assembly date and price of the complete kit to be used as a key supporting document during audit.</p> <p><strong>Recommended</strong><br /> Update the serialized (managed) SKO component lists to show all components on SKO catalog with the quantity the kit should contain (authorized) as well as actual on hand quantity. Allow for adjustment of SKO Header Record NSN price of the Kit, based on the Condition Code of the Kit. Solution must include unit value for managed and unmanaged kits.<br /> Update the DW Form 08 SKO managed kit to have the assembly date and price of the complete kit.</p> <p><strong>Mission Critical</strong><br /> Mandated per FIAR guidance and DoD policy.</p> <p><strong>Benefits</strong><br /> Benefits all DPAS users who must pass audits that build SKOs that ultimately create an end-items.  <br />Ensure moving average cost of the kitted end-item is reportable via Material Management module. Ensure general equipment, with no SKOs, maintained with the Warehouse module can apply the standard price methodology (vs moving cost avg). <br />NOTE: SOCOM has flexibility to determine if average cost or standard cost of OM&S is accepted IAW existing policy.</p> <p><strong>Users</strong><br /> ALL  users in DPAS.</p>
20194Transaction Reversal01345WarehouseArmy: USASOCNewSubmitted: 30 Aug 2018<p><strong>Description</strong><br /> The warehouse module has no reversal process for any transactions.</p> <p><strong>Recommended</strong><br /> Add a reversal process to any type of transaction within DPAS, receipts and disposals are priority. Disposal reversal is the first priority, because the record is deleted and has to be receipted if any errors. There will need to be a function code/role to restrict access.  Replicate similar process from DPAS PA.</p> <p><strong>Mission Critical</strong><br /> Mission Critical</p> <p><strong>Benefits</strong><br /> This will allow the user to reverse a transaction and correct at a faster pace.</p> <p><strong>Users</strong><br /> ALL  users in DPAS.</p>
20193Receiving function codes01344WarehouseArmy: USASOCDoneSubmitted: 30 Aug 2018<p><strong>Description</strong><br /> ASA ALT and USSOCOM have contractor operated warehouse facilities, similar to USMC Consolidated Storage Program.  As such, the contractor is permitted to do many things, but one thing they are not permitted to do is to "obligate the government".  Accepting newly procured government materiel is one of those functions that is inherently a government function, as it could result in the government being obligated to pay the vendor for services rendered.  The "Warehouse" Receipt  Acceptance action may be perceived as a government responsibility.  As such, there should be 'controls' within DPAS that permit the Acceptance action to be separately controlled from the Receipt and Verify actions within Receiving and Quality Control processes. </p> <p><strong>Recommended</strong><br /> Establish a new Role or optional two-part step for Material Acceptance for newly acquired government property, since this solution is not required in non-GOCO facilities.  Modify the Receiving and Quality Control processes to establish that newly acquired Government Material  "Acceptance" actions are Role Specific. This would mirror Government Acceptance steps for Government Acceptance of Material found in the DD Form 250 Material Inspection and receiving report. By controlling the Acceptance Step action by role, the organization can ensure that only authorized individuals can perform the acceptance step on behalf of the government.   Objective: Use WAWF acceptance/rejection transactions to inform available action options in DPAS.  For example, grey out the "Acceptance" button in DPAS until the WAWF transaction for acceptance has been completed by the government, thereby ensuring no materiel is "accepted" into the inventory until after government acceptance/vendor payment has occurred.</p> <p><strong>Mission Critical</strong><br /> Mission critical to the PEO-SOFSA (Lexington) DPAS Warehouse implementation, which will begin in FY19.</p> <p><strong>Benefits</strong><br /> Enables inherently governmental work to be accomplished by proper government civilians.  Speeds up receipt, QC and acceptance within DPAS so that it will not negatively affect performance of CTRs in GOCO facility. </p> <p><strong>Users</strong><br /> All GOCO users.</p> <p><strong>Completed – Release 2020.1 – 6 March 2020</strong></p>
20192Self-conversion Receipts01343WarehouseArmy: USASOCNewSubmitted: 30 Aug 2018<p><strong>Description</strong><br /> When receiving assets into DPAS from a non-DPAS user (either from an alternative Service supply system or a vendor), each serial number has to be entered one at a time into the verified grid, since the DD1348 does not have a 2D barcode.  This is a time-intensive and error-prone process.</p> <p><strong>Recommended</strong><br /> Allow the users to utilize a self-conversion excel for receiving mass quantities (over 100) into the Warehouse for receipts from non-DPAS users. Self conversion .xls should include all data elements of the DD1348, such as stock number, serial number, condition code, acquisition value, and acquisition date.</p> <p><strong>Mission Critical</strong><br /> Mission Critical</p> <p><strong>Benefits</strong><br /> This will allow the depots/warehouses that receive mass quantities to receipt assets at a much faster pace.</p> <p><strong>Users</strong><br /> ALL  users in DPAS.</p>
20191Inspection Action Look-Up01327WarehouseAF: AFERMSNewSubmitted: 08/29/2018<p><strong>Description</strong><br /> currently, to find out what NSN I have an inspection assigned to, I have to hit the edit button an every single NSN. This is extremely inefficient and time consuming.</p> <p><strong>Recommended</strong><br /> give me a hyper-link in the inspection action grid that works like the substitute stock number hyper-link and shows me what NSNs the inspection is assigned to.</p> <p><strong>Mission Critical</strong><br /> important</p> <p><strong>Benefits</strong><br /> allows warehouse officers to more efficiently make corrections and changes to inspections.</p> <p><strong>Users</strong><br /> ALL AFERMS</p>
20190Service Names01326WarehouseAF: AFERMSDoneSubmitted: 08/29/2018<p><strong>Description</strong><br /> Need to have Service Names added with specific capabilities.</p> <p><strong>Recommended</strong><br /> Need to have the following Service names added "LL01, LL02, LL03, LL04, LL05, LL06, LL07, LL08, SS06 and New Equipment Training"<br />These service names need to have a check box option that can be selected by warehouses to set those appointments to a minimum of 2 attending 48 hours prior or it automatically cancels the appointment.<br />These Service names also need to sync to the member profile to allow users to update sizes, there needs to be a check box under member profile to select no changes necessary. (Can provide example ideas on a powerpoint at a later date if needed)</p> <p><strong>Mission Critical</strong><br /> highly desired</p> <p><strong>Benefits</strong><br /> time savings, ability to track issue areas and data accuracy.</p> <p><strong>Users</strong><br /> All</p> <p><strong>Completed – Release 7.1 – 26 July 2019</strong></p>
20189Insp num gen01325WarehouseAF: AFERMSNewSubmitted: 08/29/2018<p><strong>Description</strong><br /> currently the QA/QC reporting function is a mess. mostly due to the fact that the inspections in the system are handled as completely different inspections and not related to each other when in actual fact they are related. for example: If an item has a 30 day and a 120 day inspection due they will be completed concurrently. The QC for that item will apply to both inspections.  a QC inspector will not perform two separate QCs on that item.  even if the QC is completed a week later, it is still treated as an extension of that inspection not a completely different inspection.</p> <p><strong>Recommended</strong><br /> change the way QC/QA/Inspection numbers(we'll call them job numbers for brevity) are generated. If you make the Job number the same for all inspections on an item completed on the same day and the QC generated from that inspection, with the exception that the final digit changes, you could clearly search for an inspection QC combo and get accurate reports. If you reserved a specific number for QC in the last digit spot it would add even more clarity 0 or 9 for instance.</p> <p><strong>Mission Critical</strong><br /> critical, the QA/QC reports are unusable as they are and require us to use an access database to track QC/QCs until the reporting function works.  It will not work without this SCR accomplished.</p> <p><strong>Benefits</strong><br /> we could see positive results form the QA/QC reports SCR we already had implemented.</p> <p><strong>Users</strong><br /> All AFERMS</p>
20188Receive Lin/Tamcn Kit01324WarehouseAF: AFERMSNewSubmitted: 08/29/2018<p><strong>Description</strong><br /> we waste a lot of time building kits that have Lin/Tamcns instead of receiving them like we do non-Lin/Tamcn kits.</p> <p><strong>Recommended</strong><br /> allow us to receive Lin/Tamcn kits.</p> <p><strong>Mission Critical</strong><br /> important</p> <p><strong>Benefits</strong><br /> huge time savings</p> <p><strong>Users</strong><br /> All Users</p>
20187deployed to home station insp01323WarehouseAF: AFERMSNewSubmitted: 08/29/2018<p><strong>Description</strong><br /> Inspections that trigger when deployed are directly tied to a home station inspection. If we switch an item from home station to deployed or vice versa, we lose visibility of the inspections that were being conducted and the item shows as grossly overdue inspection.</p> <p><strong>Recommended</strong><br /> give us the ability when assigning inspections via NSN add/update function to assign a relation between a deployed inspection and a home station inspection.</p> <p><strong>Mission Critical</strong><br /> critical currently we have to print all the data before we move between deployed and non-deployed locations then hand jam all the inspections in.</p> <p><strong>Benefits</strong><br /> Accurate data, no need to do the hand jam mentioned above</p> <p><strong>Users</strong><br /> ALL AFERMS</p>
20186sub stock nbr kits01322WarehouseAF: AFERMSNewSubmitted: 08/29/2018<p><strong>Description</strong><br /> We do not have the ability to use the substitute stock number in kitting.  There are instances when the LINTAMCN is not appropriate. For instance the blowers, these are not a sized item they just have three different stock numbers for the same thing. Or for instance sunscreen.  there are multiple stock numbers that have different .oz per unit of issue.  we need to be able to set a different qty required for the substitute stock number of a different volume per unit of issue.</p> <p><strong>Recommended</strong><br /> allow using substitute stock numbers when building kits or adding components.  allow us to set a different Qty required for the sub stock number if it is used.</p> <p><strong>Mission Critical</strong><br /> important</p> <p><strong>Benefits</strong><br /> accurate kit catalog options for users. allows us to clean up kits and the large quantity of optional components</p> <p><strong>Users</strong><br /> All AFERMS</p>
20185DW01 Revisions01321WarehouseAF: AFERMSDoneSubmitted: 08/29/2018<p><strong>Description</strong><br /> Currently we cannot view the container id (set) or location on the DW01, having this ensures<br />that units can properly account for equipment, especially equipment installed on aircraft.</p> <p><strong>Recommended</strong><br /> Add 'Container Id' and 'Location' to the DW01 printout.</p> <p><strong>Mission Critical</strong><br /> highly desired</p> <p><strong>Benefits</strong><br /> time savings and data accuracy.</p> <p><strong>Users</strong><br /> All</p> <p><strong>Completed – Release 6.3 – 21 December 2018</strong></p>
20184Form 4601320WarehouseAF: AFERMSDoneSubmitted: 08/29/2018<p><strong>Description</strong><br /> Currently we cannot sanitize (remove unit information) our Form 46, this is a requirement for our job. We also need the ability to edit the date/time and installed date on the form for our shift workers.</p> <p><strong>Recommended</strong><br /> Add option to sanitize and ability to change date/time and installed date. (See powerpoint example)</p> <p><strong>Mission Critical</strong><br /> Critical, information is on Aircraft, where Aircraft go into situations and if compromised should not have information about where the aircraft is from</p> <p><strong>Benefits</strong><br /> time savings, ability to meet requirements and data accuracy.</p> <p><strong>Users</strong><br /> All</p> <p><strong>Partially Completed – Release 6.3 – 21 December 2018</strong></p> <p><strong>Completed – Release 7.0 – 20 April 2019</strong></p>
20183ICN Condition Code Error01319WarehouseAF: AFERMSNewSubmitted: 08/29/2018<p><strong>Description</strong><br /> Hard to identify what SKO or Component has the error without searching the ICN.</p> <p><strong>Recommended</strong><br /> Add the Item Description and Serial Number(if it has one) to the error given on all screens that give these types of errors. Should work the same way on any other errors that currently only give an ICN identifier. (see powerpoint for two examples)</p> <p><strong>Mission Critical</strong><br /> highly desired</p> <p><strong>Benefits</strong><br /> time savings and data accuracy.</p> <p><strong>Users</strong><br /> All</p>
20182Appointment Walk-Ins / No-Shows01318WarehouseAF: AFERMSDoneSubmitted: 08/29/2018<p><strong>Description</strong><br /> Need ability under warehouse mgmt-scheduling-appointments to add appointments that are in the past and need to be able to edit check in/check out date/time to account for walk-in.  Also need to be able to select walk-in as a priority when adding an appointment. Lastly, need a box to select for No Show that closes the appointment (see powerpoint)</p> <p><strong>Recommended</strong><br /> Add these abilities in either the grid and/or the edit pop-up (can provide more ideas later if needed)</p> <p><strong>Mission Critical</strong><br /> highly desired</p> <p><strong>Benefits</strong><br /> time savings, ability to track issue areas and data accuracy.</p> <p><strong>Users</strong><br /> All</p> <p><strong>Completed – Release 7.2.00 – 8 November 2019</strong></p>
20181Unit Return Movement01317WarehouseUSMC: CSPRemovedSubmitted: 23 Aug 2018<p><strong>Description</strong><br /> Currently DPAS-WM has Unit Issues/Returns under Inquires>Unit Issue>Unit Issue Activity.  Recommend that Unit Issues/Returns functionality be moved to the Inquiries>Issue/Return Activity process.     </p> <p><strong>Recommended</strong><br /> Recommend that Unit Issues/Returns functionality be Moved to the Inquiries>Issue/Return Activity Process. </p> <p><strong>Mission Critical</strong><br /> Yes, this will help increase the speed and proficiency during the process of pulling reports on all Unit issues and returns. </p> <p><strong>Benefits</strong><br /> Having this inquiry moved will help with the speed and proficiency during the reporting and research process. thus reducing the labor time used pulling reports.</p> <p><strong>Users</strong><br /> All IIF</p> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20180Warehouse Activity Reports01316WarehouseSOCOMNewSubmitted: 17 Aug 2018<p><strong>Description</strong><br /> There is no specific report for Registry Reporting in the Warehouse or Materiel Management modules.</p> <p><strong>Recommended</strong><br /> To allow Registry to filter the non-reportable assets from reportable for the canned reports and inquiries, request the following solutions:</p> <ul> <li><em>Threshold:</em> add both Reportable Cd and CIIC to the following Warehouse Inquiries: Stock Nbr Inquiry, ICN Inquiry, and Expiring Items Inquiry.  Add both Reportable Cd and CIIC to the Material Management module Inquiry for Inventory Transaction.</li> <li><em>Objective:</em> add the Reportable Cd and CIIC from the catalog to all the Reports and Inquiry grid options in Warehouse Module.</li> <li>Consider using the Reportable Code to dictate in the enterprise catalog what items are registry reportable.</li> </ul> <p><strong>Mission Critical</strong><br /> Mandated per Registry Policy by DoD.</p> <p><strong>Benefits</strong><br /> Enables reports to be quickly filtered for Registry's reporting requirements.</p> <p><strong>Users</strong><br /> ALL USERS</p>
20179DEAMS Interface01315WarehouseSOCOMNewSubmitted: 7 Aug 2018<p><strong>Description</strong><br /> The warehouse module has no interface to DEAMS, USSOCOM's financial reporting system of record.</p> <p><strong>Recommended</strong><br /> Establish an interface to between DPAS and DEAMS to pass all relevant financial data.</p> <p><strong>Mission Critical</strong><br /> Mission Critical</p> <p><strong>Benefits</strong><br /> Reduces Time/Cost, Improves accuracy, accountability and financial reporting</p> <p><strong>Users</strong><br /> ALL  users in DPAS.</p>
201782x1.25 Labels-DPAS WM01314EnterprisePFPANewSubmitted: 7/25/18<p><strong>Description</strong><br /> 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.</p> <p><strong>Recommended</strong><br /> It is recommended that the option of printing 2x1.25 barcode labels be added. This label should include the item desc, size, and location.</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> 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.</p> <p><strong>Users</strong><br /> This affects all WM users</p> <p><strong>**08/03/2018 - This is an UPDATE/REPLACEMENT to <a href="index.php/support/system-change-request/details/4/20177/2x1-labels-for-dpas-wm">SCR 01313</a>.**</strong></p>
201772x1 Labels for DPAS WM01313EnterprisePFPARemovedSubmitted: 7/25/18<p><strong>Description</strong><br /> 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.</p> <p><strong>Recommended</strong><br /> It is recommended that the option of printing 2x1 bar-code labels be added. This label should include the item description, size, and location.</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> This solution would enable PFPA to utilize the same size barcode labels as the WM and ensure that correct labels are placed on assets.</p> <p><strong>Users</strong><br /> This affects all WM users</p> <p><strong>**08/03/2018 - This is REPLACED by <a href="index.php/support/system-change-request/details/4/20178/2x1-25-labels-dpas-wm">SCR 01314</a>.**</strong></p>
20176Update Equpt Util Form01311MUOSDNewSubmitted: 17 July 2018<p><strong>Description</strong><br /> Updated form to add pertinent fields the "Dispatch To" would need to capture data. All new suggested information is in "Red".</p> <p><strong>Recommended</strong><br /> 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.</p> <p><strong>Mission Critical</strong><br /> Information is mandated but currently listed on up to 5 different documents.  Looking to add to one form if possible.</p> <p><strong>Benefits</strong><br /> Paperwork and time reduction.  Can load one form to Dispatch AU for historical records.</p> <p><strong>Users</strong><br /> Only users that Dispatch.</p>
20175M&U Dispatched To Contact Information01310MUOSDNewSubmitted: 17 July 2018<p><strong>Description</strong><br /> Expedite the closing of "Over Due Returns", it would be good to have Operators contact information available.</p> <p><strong>Recommended</strong><br /> 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.</p> <p><strong>Mission Critical</strong><br /> Mandated at Agency level to reduce unavailable vehicles due to lack of timely return.</p> <p><strong>Benefits</strong><br /> Reduces time of finding POC information. </p> <p><strong>Users</strong><br /> Would benefit all users.</p>
20174Roles Administrator01309EnterpriseSOCOMNewSubmitted: 13 July 2018<p><strong>Description</strong><br /> 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.<br />  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. </p> <p><strong>Recommended</strong><br /> 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.  </p> <p><strong>Mission Critical</strong><br /> 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.</p> <p><strong>Benefits</strong><br /> 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</p> <p><strong>Users</strong><br /> 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.</p>
20173Program Manager Functions01308EnterpriseAF: OtherNewSubmitted: 7/12/2018<p><strong>Description</strong><br /> 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. </p> <p><strong>Recommended</strong><br /> 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. </p> <p><strong>Mission Critical</strong><br /> Yes.  There is a requirement that is needed to replace the existing functionality within AFEMS / CERT / D200. </p> <p><strong>Benefits</strong><br /> Enables the Air Force to migrate the equipment accounts from ILS-S to DPAS and sunset AFEMS.</p> <p><strong>Users</strong><br /> 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. </p>
20172Allocation Standards Mgmt01307EnterpriseAF: OtherDoneSubmitted: 7/12/2018<p><strong>Description</strong><br /> 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.</p> <p><strong>Recommended</strong><br /> 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. </p> <p><strong>Mission Critical</strong><br /> Yes.  There is a requirement that is needed to replace the existing functionality within AFEMS. </p> <p><strong>Benefits</strong><br /> Enables the Air Force to migrate the equipment accounts from ILS-S to DPAS and sunset AFEMS.</p> <p><strong>Users</strong><br /> 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. </p> <p><strong>Completed – Release 7.0 – 20 April 2019</strong></p>
20171Editable Service Life Expiration01306WarehouseAF: AFERMSDoneSubmitted: 14 May 2018<p><strong>Description</strong><br /> 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. </p> <p><strong>Recommended</strong><br /> 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.</p> <p><strong>Mission Critical</strong><br /> Critical, the system doesn't forecast correctly at this time, so the system isn't working for what it is intended to work.</p> <p><strong>Benefits</strong><br /> time savings and accurate data reporting.</p> <p><strong>Users</strong><br /> all</p> <p><strong>Completed – Release 6.2.2 – 21 September 2018</strong></p>
20170CMOS support as a TMO for the PA User01305PAAF: OtherDoneSubmitted: 7/12/2018<p><strong>Description</strong><br /> 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.</p> <p><strong>Recommended</strong><br /> Incorporate the use of CMOS within the Asset Transfer and Disposition processes for the movement of equipment. </p> <p><strong>Mission Critical</strong><br /> 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. </p> <p><strong>Benefits</strong><br /> Enables the Air Force to migrate the equipment accounts from ILS-S to DPAS and sunset AFEMS.</p> <p><strong>Users</strong><br /> This impact all AF organizations, and possibly other organizations that use CMOS as their TMO system.</p> <p><strong>Completed – Release 7.1 – 26 July 2019</strong></p>
20169Create / Manage a Requisition that will create a Due In in the PA module01304EnterpriseAF: OtherDoneSubmitted: 7/12/2018<p><strong>Description</strong><br /> 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.</p> <p><strong>Recommended</strong><br /> 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.</p> <p><strong>Mission Critical</strong><br /> 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. </p> <p><strong>Benefits</strong><br /> Enables the Air Force to migrate the equipment accounts from ILS-S to DPAS and sunset AFEMS.</p> <p><strong>Users</strong><br /> This change could impact a large group of DPAS, both AF and other.</p> <p><strong>Completed – Release 7.0 – 20 April 2019</strong></p>
20168SA/LW Registry Capability01303EnterpriseAF: OtherDoneSubmitted: 7/12/2018<p><strong>Description</strong><br /> 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.</p> <p><strong>Recommended</strong><br /> 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.</p> <p><strong>Mission Critical</strong><br /> Yes.  There is a requirement to provide special handling / reporting for SA/LW.  This function must be subsumed by DPAS as AFEMS is sunset. </p> <p><strong>Benefits</strong><br /> 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.</p> <p><strong>Users</strong><br /> All users who are involved with managing SA/LWs.</p> <p><strong>Completed – Release 7.0 – 20 April 2019</strong></p>
20167DPAS / AFWAY Web Service Interface01302PAAF: OtherDoneSubmitted: 7/12/2018<p><strong>Description</strong><br /> 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.</p> <p><strong>Recommended</strong><br /> Create a Web Service Interface that will provide AFWAY with the data it requires.</p> <p><strong>Mission Critical</strong><br /> Yes.  This data is the only method that authorizes the IT Custodians to have visibility of IT orders in AFWAY.</p> <p><strong>Benefits</strong><br /> Providing information concerning the IT Custodians in DPAS to AFWAY will permit the IT Custodians to have visibility of IT orders within AFWAY.</p> <p><strong>Users</strong><br /> All Air Force IT Custodians</p> <p><strong>Partially Completed – Release 6.3.3 – 22 February 2019</strong></p> <p><strong>Completed – Release 7.0 – 20 April 2019</strong></p>
20166Lock Est Labor Hours field to a mandatory field and add error indicator01301MUAF: VSCOSNewSubmitted: 9 July 2018<p><strong>Description</strong><br /> 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.</p> <p><strong>Recommended</strong><br /> 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.</p> <p><strong>Mission Critical</strong><br /> 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.</p> <p><strong>Benefits</strong><br /> 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.</p> <p><strong>Users</strong><br /> 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.  </p>
20165Update Open Work Order Screen01300MUAF: VSCOSNewSubmitted: 07/05/2018<p><strong>Description</strong><br /> 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.</p> <p><strong>Recommended</strong><br /> 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.</p> <p><strong>Mission Critical</strong><br /> 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. </p> <p><strong>Benefits</strong><br /> 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.</p> <p><strong>Users</strong><br /> All Air Force Fleet Managers/Maintenance controllers and Material specialists utilize this information for day to day fleet management purposes.  </p>
20164Improve Performance of Master Issue List to UIC association01299WarehouseLeidosNewSubmitted: 6/26/2018<p><strong>Description</strong><br /> 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.</p> <p><strong>Recommended</strong><br /> 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.</p> <p><strong>Mission Critical</strong><br /> 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.</p> <p><strong>Benefits</strong><br /> Performance of the system.</p> <p><strong>Users</strong><br /> All users.</p>
20163Attachments for ICNs01298WarehouseNavy: NAVAIRRemovedSubmitted: 6/20/2018<p><strong>Description</strong><br /> 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.</p> <p><strong>Recommended</strong><br /> Allow Attachments at the ICN level through Inventory Update and During the Receiving Process for the following file types:</p> <ul> <li>jpeg,</li> <li>pjpeg,</li> <li>png,</li> <li>x-png,</li> <li>gif,</li> <li>pdf,</li> <li>MS Office (Word, Excel, Power Point)</li> </ul> <p><strong>Mission Critical</strong><br /> 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.</p> <p><strong>Benefits</strong><br /> 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.</p> <p><strong>Users</strong><br /> All users can benefit from being able to attach records, pictures, files to an ICN.</p> <p><strong>26Jun2018 – cancelled per Randy Reed </strong> <br /> This is the same as <a href="index.php/support/system-change-request/details/4/19952/associate-receipt-documents-to-serialized-inventory">SCR 01126</a>.</p>
20162Add City State Location Table Update01297PANavyRemovedSubmitted: 20 JUNE 2018<p><strong>Description</strong><br /> 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. </p> <p><strong>Recommended</strong><br /> 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.</p> <p><strong>Mission Critical</strong><br /> 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. </p> <p><strong>Benefits</strong><br /> Adding these fields will add visibility of the actual physical address location of an asset relative to inventory and financial accountability.</p> <p><strong>Users</strong><br /> Would affect any users of the Property Accountability module DoD wide.</p> <p>***</p> <p>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.</p> <p>***</p> <p><strong>21 Aug 2019 – cancelled per Kevin Callahan </strong> <br /> No Longer Required.</p>
20161Upcoming Work Report01296MUArmyNewSubmitted: 6/21/2018<p><strong>Description</strong><br /> 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.</p> <p><strong>Recommended</strong><br /> 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.</p> <p><strong>Mission Critical</strong><br /> Critical accurate forecasting ensures customers know when they need to have equipment dropped off to be serviced (work order completed).  </p> <p><strong>Benefits</strong><br /> 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.</p> <p><strong>Users</strong><br /> I believe it probably affects all M&U concerned individuals</p>
20160Utilization Report Extract Improvement01295MUDLANewSubmitted: 20180620<p><strong>Description</strong><br /> 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.</p> <p><strong>Recommended</strong><br /> 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.<br /> Each and every asset placed in DPAS must have a SN created, regardless of agency.<br /> 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.<br />  Using the two fields the calculation should be:</p> <ul> <li>Util SVC Life (250000)/Yr SVC Life (10)= Util Target Annual (25000)</li> <li>Util Target Annual (25000)/12 (months)=Util Target Monthly (2083)</li> </ul> <p>The formula is agency neutral, it is the data in the fields that drive the end result.<br /> This should be the case regardless of type of asset.<br /> And that value should populate the Util Target Monthly in the MAM, as well as the report.<br /> These values are already being utilized to develop the Utilization Report Extract.<br /> 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.</p> <p><strong>Mission Critical</strong><br /> This is mission critical because it supports tracking proper use of assets and tracking of under utilized assets correctly.</p> <p><strong>Benefits</strong><br /> 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.</p> <p><strong>Users</strong><br /> This should affect ALL users utilizing DPAS.</p>
20159QC Completion Date01294WarehouseAF: AFERMSNewSubmitted: 20 Jun 2018<p><strong>Description</strong><br /> For AFE a QC is an inspection of an inspection.  currently we can create a QC from an inspection, but from there the two inspections are in no way related in the system.  If I complete an inspection at the end of the month and the QC is not completed until the beginning of the next month, it screws up the % reporting for two months. It shows a shortfall for the month the inspection was accomplished and an overage for month the QC was accomplished.</p> <p><strong>Recommended</strong><br /> make the completion date of the QC default to the completion date of the inspection it was created from.</p> <p><strong>Mission Critical</strong><br /> critical.  our percentage reporting is worthless without it. Manual tracking systems have to be implemented until this is corrected.</p> <p><strong>Benefits</strong><br /> many man/hours scouring QC results inquiry matching up inspection with QCs and manually calculating percentages.</p> <p><strong>Users</strong><br /> All AFERMS</p>
20158CBRN Gear Report Format01293WarehouseLeidosNewSubmitted: 14 June 2018<p><strong>Description</strong><br /> The CBRN gear formatting as currently designed is confusing to the users with the on-hand quantity being duplicated on all NSNs within a warehouse. It also takes to long to produce the report when it includes all the individual warehouse tabs.</p> <p><strong>Recommended</strong></p> <ol> <li>Modify the format of the report to include the On-Hand Quantity = 0 for each Warehouse.</li> <li>Remove the additional Warehouse tabs on the report and only show the Summary page.</li> </ol> <p><strong>Mission Critical</strong><br /> Yes. This report is used to track CBRN gear through the LP.</p> <p><strong>Benefits</strong><br /> .</p> <p><strong>Users</strong><br /> Yes.</p>
20157Power User Tool01292WarehouseLeidosNewSubmitted: 14 June 2018<p><strong>Description</strong><br /> Users currently have no way to merge two EDI PIs if a member has two EDI PIs assigned to them. The users have to submit a ticket to the DPAS Help Desk and have a script run to merge the two EDI PIs for the Member.</p> <p><strong>Recommended</strong><br /> Develop a "Power User Tool" screen that will allow select and limited number of users the ability to enter the users two EDI PIs and merge them from the UI. Will decrease the amount of time between completion and the number of Help Desk tickets.</p> <p><strong>Mission Critical</strong><br /> Yes. Will decrease the amount of time between completion and the number of Help Desk tickets.</p> <p><strong>Benefits</strong><br /> Reduces time between completion.</p> <p><strong>Users</strong><br /> Power Users</p>
20156Inventory Activity Columns01291WarehouseUSMC: CSPRemovedSubmitted: 07 June 2018<p><strong>Description</strong><br /> Currently there is no Physical Inventory Number or Issued DODAAC Columns in Inventory Activity.  </p> <p><strong>Recommended</strong><br /> For Audit purposes recommend that the Physical Inventory Number and Issued DODAAC columns be added to Grid Options Columns In Inventory Activity.</p> <p><strong>Mission Critical</strong><br /> Yes this will help with audit purposes to be able to show the physical inventory number for all Loss or Gain transaction.  Also to be able to view the issued DODAAC for warehouse issues and MRO's instead of having to go to multiple areas to get this information.  Thus helping with reports that are required on a monthly basis.</p> <p><strong>Benefits</strong><br /> Having this functionality will help from having to go through multiple steps to get the information we need for Audit Purposes.</p> <p><strong>Users</strong><br /> All IIF/UIF</p> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20155Render Reconciliation Reports in Excel Format01290EnterpriseDMANewSubmitted: 07 JUN 18<p><strong>Description</strong><br /> PDF format is how recon reports render.  </p> <p><strong>Recommended</strong><br /> Produce the inventory reconciliation report in Excel format</p> <p><strong>Mission Critical</strong><br /> Yes, excel allow the user to sort and arrange columns, pdf does not</p> <p><strong>Benefits</strong><br /> better inventory management and customer service</p> <p><strong>Users</strong><br /> Yes, most definitely, excel is truly a best business practice app for inventory control, I don't understand why DPAS does not already have this.</p>
20154ICN Inventory Inquiry Secondary Serial Number Column Addition01289WarehouseUSMC: DMCRemovedSubmitted: 6/6/2018<p><strong>Description</strong><br /> DMC (MFSC) is starting to use the secondary serial number field to track purpose codes on ICN's. Currently there is no way to see the secondary serial number field except in inventory update manager. When looking for components of SKO's we will be unable to see the secondary serial number on the component in inventory update manager. Also when pulling queries from ICN Inventory inquiry at the LP level we will not be able to see the secondary serial numbers for any items.</p> <p><strong>Recommended</strong><br /> Recommending that the secondary serial number column be added to the ICN Inventory Inquiry. This will allow us to see the secondary serial number (purpose code for our purpose) at the component level when needed. This also allows us to pull the data at the Logistics program level</p> <p><strong>Mission Critical</strong><br /> This is mission critical because we need the ability to pull secondary serial numbers information at the LP level for component and over end items.</p> <p><strong>Benefits</strong><br /> This will reduce the time it takes to put together data as well improve the accuracy</p> <p><strong>Users</strong><br /> This will affect any users who use the secondary serial number and want to see those serial numbers at the Logistics Program level.</p> <p><strong>11June2018 – cancelled per Scott Prouse </strong> <br /> This is a duplicate of <a title="SCR 01288" href="index.php/support/system-change-request/details/4/20153/grid-options">SCR 01288</a>.</p>
20153Grid Options01288WarehouseNavy: NAVAIRDoneSubmitted: 5APR18<p><strong>Description</strong><br /> Command and process required fields are missing from the grid options for multiple inquiries and processes.</p> <p><strong>Recommended</strong><br /> Add Secondary Serial Number to the following Grid Options columns lists:</p> <ul> <li>ICN Inquiry</li> <li>Unit Issue Outstanding Items Inquiry</li> <li>Unit Return: Outstanding Items Grid</li> <li>Conduct Physical Inventory</li> </ul> <p>Estimated Return Date needs to be added to the Grid Options for Unit Issue – Outstanding Items Inquiry</p> <p><strong>Mission Critical</strong><br /> Mission Critical. We use the Secondary Serial Number to identify specific inventory. It must be included on these inquiries. Our processes are also driven by the estimated return dates for tools that we've sent out through the Unit Issue process, and should be included on the Outstanding Items Inquiry.</p> <p><strong>Benefits</strong><br /> Implementing this solution reduces the time and cost for locating data for reports, inventories, and provides accurate accountability and cost avoidance.</p> <p><strong>Users</strong><br /> This certainly affects all users within the NAVAIR ST/STE LP, and will be a welcome update for all DPAS users.</p> <p><strong>Completed – Release 6.2 – 31 August 2018</strong></p>
20152Warehouse Roles01287WarehouseNavy: NAVAIRNewSubmitted: 5APR18<p><strong>Description</strong><br /> Role creation for Managing Special Tooling and Special Testing Equipment</p> <p><strong>Recommended</strong><br /> Create 2 new Roles in the DPAS Warehouse Module that fit our business processes. See Attached Spreadsheet for a breakdown of each role requirement.</p> <p><strong>Mission Critical</strong><br /> Mission Critical - The Current Roles are insufficient to meet NAVAIRs needs for ST/STE management</p> <p><strong>Benefits</strong><br /> Reduces Time/Cost for Training, Gives proper amount of access to personnel, Improves data security, provides access to vital processes required to conduct NAVAIR business.</p> <p><strong>Users</strong><br /> Required for all users transitioning from eTIMS to DPAS for ST/STE management.</p>
20151One Time Repair Limit Report Enhancement01286MUDLANewSubmitted: 5/16/2018<p><strong>Description</strong><br /> Problem: There's no way to know determine if the repairs will exceed a one time repair limit.</p> <p><strong>Recommended</strong><br /> Add the capability to display the One Time repair Limit per asset on an Open Work Order and also there should be a way to pull this information as well. This repair limitation factor needs to be established on the PA side and shown on the M&U side. It should only be accessible to the Property Administrator and Agency level.</p> <p><strong>Mission Critical</strong><br /> This is mission critical because it will assist fleet managers and maintenance managers when monitoring, analyzing replacement, and assigning repairs for equipment. The One Time repair Limit should equal the dollar limit for one time repair without getting prior HQ approval. This repair limitation factor has to be set by HQs or OSD. The repair limitation factor is multiplied by estimated replacement cost equals the one time repair limit in dollars shown on the maintenance work order.</p> <p><strong>Benefits</strong><br /> This will benefit all activities in DPAS by providing a better tool for Fleet Managers, supervisors, and maintenance managers to utilize and monitor, analyze and assign repairs of equipment.</p> <p><strong>Users</strong><br /> This should affect ALL users within DLA and DoD utilizing DPAS.</p>
20150Overtime Hours01285MUDLANewSubmitted: 5/16/2018<p><strong>Description</strong><br /> When pulling the Work Order Inquiry there's no way to show overtime hours performed on any particular work order. There's also no way to filter for overtime work performed or billed from the Search Criteria page. There are fields for Actual Labor Hours and Non-labor Hours, but nothing for Actual Overtime Hours.</p> <p><strong>Recommended</strong><br /> Add Actual Overtime Hours to the search Criteria and as one of the selections under Fields.</p> <p><strong>Mission Critical</strong><br /> Mandated. This is a requirement to be able to identify any overtime work that will be charged to PMs and unscheduled work performed by our contractors and the ability to monitor the amount of overtime needed to maintain our fleet.</p> <p><strong>Benefits</strong><br /> Benefits will be the proper accounting of overtime hours taken by technicians and charged by the contractors.</p> <p><strong>Users</strong><br /> All DLA Fleet managers/maintenance supervisors will be affected by this.</p>
20149Equipment Pool Asset Report Enhancement01284MUDLANewSubmitted: 5/16/2018<p><strong>Description</strong><br /> Problem: Fleet Managers need the ability to pull the Equipment Pool Asset Report by ACBTL UIC and also include the cumulative Maintenance Cost for each asset within that Equipment Pool.</p> <p><strong>Recommended</strong><br /> Enhance the Equipment Pool Asset report so that it's able to be pulled by at the ACTBL UIC. Currently, the Equipment Pool Asset report can only be run per UIC. Also, enhance the report to include the cumulative maintenance cost for each asset within the equipment pool.</p> <p><strong>Mission Critical</strong><br /> This is mission critical because it will assist fleet managers and maintenance managers when monitoring, analyzing, and assigning equipment within the equipment pool. This will also improve better visibility to leadership on trends per equipment pool, as well as when evaluating contracts.</p> <p><strong>Benefits</strong><br /> This will benefit all activities in DPAS by providing a better tool for Fleet Managers, supervisors, maintenance managers and CORs to utilize and monitor, analyze and assign equipment within the respected equipment pool and ACTBL UIC.</p> <p><strong>Users</strong><br /> This should affect ALL users within DLA and DoD utilizing DPAS.</p>
20148Service Life Expiration Extension01283WarehouseAF: AFERMSNewSubmitted: 14 May 2018<p><strong>Description</strong><br /> 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. </p> <p><strong>Recommended</strong><br /> 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.</p> <p><strong>Mission Critical</strong><br /> Critical, shows items expiring before their due date wasting funding buying items not needed. Also doesn't allow for replacing supply shortages.</p> <p><strong>Benefits</strong><br /> time savings and accurate data reporting.</p> <p><strong>Users</strong><br /> all</p>
20147Requisition Process01282EnterpriseLeidosNewSubmitted: 05/10/2018<p><strong>Description</strong><br /> DPAS <a href="index.php/support/system-change-request/details/4/13705/warehouse-requisitions">SCR 00726</a> provided DPAS with MILSTRIP requisitioning capabilities within the Materiel Mgmt module.  Currently, this requisitioning process requires a Warehouse to be associated to the ICP that is placing order.  With additional Customers transitioning to DPAS, there is a need to provide additional capabilities required to be supported.</p> <p><strong>Recommended</strong><br /> It is recommended that the following capabilities be added to the current requisition processes:</p> <ol> <li>Management of Funds – Be able to establish Fund Targets which Total Funds Authorized, Funds Committed, Fund Amount Obligated and remaining balance available by Fund Type.</li> <li>Ability for ICP to turn off DLMS interfaces.</li> <li>Ability for ICP to manually update the status of a requisition.  <br />This is required for off line purchases.</li> <li>ICP Requisition History Inquiry</li> <li>ICP DLMS transaction Inquiry</li> <li>Ensure the Ordering Process is fully SLOA compliant.  <br />Determine Agency Qualifier Code for DLMS transactions (Financial_Accounting_Data Segment).</li> <li>Support Materiel Obligation Validation - DLM 4000.25 Chapter 8 - DLMS 517M.</li> <li>Develop a Web Service with DoD Financial Systems to check for Funds Availability.</li> <li>Create a connector that can be used to interface with DoD Procurement Systems – transmitting purchase requests, mod requests and receiving procurement orders/updates.</li> <li>Incorporate a Document Nbr Generator selector that provides for multiple Document Series for like Procurements.</li> <li>Enhance the process to take advantage of DLMS capabilities not currently provided for.</li> <li>Be able to place an order without being connected to a Warehouse.  <br />This would be support purchased for PA Assets – Create Due In and maintain status of the Due in throughout the order to receipt process, and for Direct Vendor Shipments that would not be shipped to a warehouse for receipt.</li> <li>Provide access to the Requisition processes from within the PA Module to support.</li> </ol> <p><strong>Mission Critical</strong><br /> FIAR compliance is mandated.  This change is considered a necessary feature to improve the audit trail to ensure FIAR compliance.</p> <p><strong>Benefits</strong><br /> Improves the audit trail.</p> <p><strong>Users</strong><br /> </p>
20146M&U Inquiry Adds - for FAST Reporting01281MUOSDNewSubmitted: 09 May 2018<p><strong>Description</strong><br /> Cannot run M&U Inquiries on vehicle characteristics.</p> <p><strong>Recommended</strong><br /> Request adding the following fields and drop-down tables to the M&U Maintenance Asset Inquiry Search Criteria and to the Inquiry Fields:</p> <ul> <li>Fuel Configuration Code</li> <li>EISA Acquisition Code</li> <li>EPAct 2005 Designation Code</li> </ul> <p><strong>Mission Critical</strong><br /> No but it will assist Fleet Managers validate FAST data easier by pinpointing specific fields for segregation.</p> <p><strong>Benefits</strong><br /> Reduces time and increases data validation accuracy of FAST data.</p> <p><strong>Users</strong><br /> Just users of FAST Reportable assets.</p>
20145Commodity Manager View01280WarehouseSPECWARCOMNew04/17/2018<p><strong>Description</strong><br /> Need to display a roll up of assets with their O/H quantity and associated BOI/Allowance for each Site/Region/Warehouse</p> <p><strong>Recommended</strong><br /> Need a view or query within WH that allow senior leadership in put a BOI/Allowance for each stock number. Once that has been entered, then the O/H quantity and BOI/Allowance need to 'roll up' when the data is being viewed at the Site or Region level.</p> <p><strong>Mission Critical</strong><br /> This is not mission critical or mandated. However, this is a feature that is beneficial for armory and commodity managers to monitor current inventory levels compared to approved inventory levels.</p> <p><strong>Benefits</strong><br /> This solution improves accuracy of financial reporting and reduces data calls and promulgation of inaccurate information.</p> <p><strong>Users</strong><br /> Yes, this will affect all users within NSW armories.</p>
20144Create Dashboard Capability01279WarehouseSPECWARCOMNewSubmitted: 04/17/2018<p><strong>Description</strong><br /> Need to create a data 'dashboard' capability similar the SWIFT system NSW armory users are using today. Examples of current tool can be provided</p> <p><strong>Recommended</strong><br /> The data 'dashboard' should include graphs, charts, and raw numbers that are comprised of the following data elements (similar to the tool used today):</p> <ol> <li>Armory and Inventory Maintenance Scores: <ol style="list-style-type: upper-alpha;"> <li>Region, Site, Warehouse roll up capability</li> <li>Display Qty of assets O/H (distinguished by secure commodity) for each Site, Region, Warehouse</li> <li>Display Overdue Inventory Records for each Site, Region, Warehouse</li> <li>Display Inventory score for each Site, Region, Warehouse</li> <li>Display the O/H qty of 'assessable' assets for each Site, Region, Warehouse</li> <li>Display Overdue Assessment Records for each Site, Region, Warehouse</li> <li>Display Assessment score for each Site, Region, Warehouse</li> </ol> </li> <li>Recent Assessments: <ol style="list-style-type: upper-alpha;"> <li>Region, Site, Warehouse roll up capability</li> <li>Display Reportable Commodity</li> <li>Display items assessed for each Reportable Commodity</li> <li>Display items that 'passed' assessment for each Reportable Commodity</li> <li>Display items that 'passed w/repair' assessment for each Reportable Commodity</li> <li>Display items that 'failed' assessment for each Reportable Commodity</li> </ol> </li> <li>Upcoming Assessments: <ol style="list-style-type: upper-alpha;"> <li>Region, Site, Warehouse roll up capability</li> <li>Display Reportable Commodity</li> <li>Display 'Overdue' assessment for each Reportable Commodity</li> <li>Display 'Assessment Due in 30 days' for each Reportable Commodity</li> <li>Display 'Assessment Due in 60 days' for each Reportable Commodity</li> <li>Display 'Assessment Due in 90 days' for each Reportable Commodity</li> <li>Display 'Assessment Due in 180 days' for each Reportable Commodity</li> </ol> </li> </ol> <p><strong>Mission Critical</strong><br /> This is not mission critical or mandated. However, this is a feature that is extremely beneficial for armory and commodity managers to monitor the effectiveness and/or deficiencies of NSW Armory operations.   </p> <p><strong>Benefits</strong><br /> This solution improves accountability, reliability, accuracy, and overall armory performance.</p> <p><strong>Users</strong><br /> Yes, this will affect all users within NSW armories.</p>
20143Legacy Data Table01278WarehouseSPECWARCOMNewSubmitted: 04/17/2018<p><strong>Description</strong><br /> Need to incorporate a query-able table within DPAS WH in order to view legacy records from previous inventory system (SWALIS).</p> <p><strong>Recommended</strong><br /> Build a query-able table within the WH application that WH users can use to perform searches for legacy asset history. NSW will provide a sample data file when requested by Leidos.</p> <p><strong>Mission Critical</strong><br /> This is a mandated requirement. NSW requires access to a minimum of 10 years of historical information on all serialized assets.</p> <p><strong>Benefits</strong><br /> This solution will maintain accountability requirements for serialized weapons and VAS assets.</p> <p><strong>Users</strong><br /> Yes, this affects all users within NSW, not just Armory. This will help bridge the gap and answer any questions resulting from the commands migration of their legacy system to DPAS WH.</p>
20142Improve Disposal Process01277WarehouseSPECWARCOMNewSubmitted: 04/17/2018<p><strong>Description</strong><br /> Need to modify current disposal capability for assets that have been disposed/archived. Once a Disposal is executed and finalized we need the full item history for the asset to be query-able and exportable.</p> <p><strong>Recommended</strong><br /> Incorporate the following features into WH for assets that have been disposed/archived:</p> <ol> <li>Once Disposal is executed, need item history available</li> <li>After a serialized item is disposed, need asset to remain in an archived status (similar to PA)</li> <li>Need to have ability to bring back disposed assets (serialized) back to life</li> </ol> <p><strong>Mission Critical</strong><br /> This is a mandated requirement. NSW and OPNAV requires access to historical information on all disposed serialized assets.</p> <p><strong>Benefits</strong><br /> This solution will maintain required accountability requirements for serialized weapons and VAS assets that have been placed in a disposal status.</p> <p><strong>Users</strong><br /> Yes, this affects all users within NSW, not just Armory. Many of our depts within NSW need the ability to bring disposed assets back to life from time to time.</p>
20141Asset Upload01276WarehouseDPASNewSubmitted: 04/23/2018<p><strong>Description</strong><br /> Currently DPAS Warehouse does not support the ability to perform a mass upload within the receipt process.  Provide a process where users can mass upload assets into DPAS Warehouse.</p> <p><strong>Recommended</strong><br /> Create Mass upload template and menu so multiple assets may be uploaded to a warehouse within one process.</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> Reduced time of entry and conversion labor hours</p> <p><strong>Users</strong><br /> Yes</p>
20140freeze01275WarehouseAF: AFERMSDoneSubmitted: 15 Apr 2018<p><strong>Description</strong><br /> in the event of an aircraft accident we would like the ability to lock a location down</p> <p><strong>Recommended</strong><br /> we would like the ability for anyone to freeze locations. we need the unfreeze ability to be given to a regional role</p> <p><strong>Mission Critical</strong><br /> critical.  involves accident investigations</p> <p><strong>Benefits</strong><br /> allows investigators to access unadulterated data</p> <p><strong>Users</strong><br /> AFE and USMC</p> <p><strong>Completed -- Release 2021.2 - 28 May 2021</strong></p>
20139add attachments to containers01274WarehouseAF: AFERMSDoneSubmitted: 15 Mar 2018<p><strong>Description</strong><br /> we have documents that go with our containers.  For instance HAZDECs for cargo shipment</p> <p><strong>Recommended</strong><br /> allow adding multiple attachments to containers. allow deleting old attachments in containers.</p> <p><strong>Mission Critical</strong><br /> important</p> <p><strong>Benefits</strong><br /> can store documents with equipment and have global access</p> <p><strong>Users</strong><br />all</p> <p><strong>Completed – Release 6.3 – 21 December 2018</strong></p>
20138DRRS01273WarehouseAF: AFERMSNewSubmitted: 15 Mar 2018<p><strong>Description</strong><br /> We have to report status of certain NSNs in DRRS (defense readiness reporting system). current systems require manual input of equipment availability and condition.</p> <p><strong>Recommended</strong><br /> connect a DPAS feed to DRRS. at the stock item level we will need a check box to flag the NSN as a DRRS feed item.  It needs to be at the stock item level because not every unit will report the same NSN in DRRS depending on mission.</p> <p><strong>Mission Critical</strong><br /> reporting is mandated by DoD instruction</p> <p><strong>Benefits</strong><br /> accurate data for combatant commanders to asses readiness.</p> <p><strong>Users</strong><br /> all</p>
20137serial update print buttons on inv mgr grid01272WarehouseAF: AFERMSNewSubmitted: 15 Mar 2018<p><strong>Description</strong><br /> we need to minimize multiple tab usage to reduce software time to our troops our spending more time on physicals tasks and less on recording them.</p> <p><strong>Recommended</strong></p> <p><strong>Mission Critical</strong><br /> on inventory update manager, selected inventory tab and the buttons "print DW01", "print expiring label"</p> <p><strong>Benefits</strong><br /> one stop shop - saves huge amount of time when trying to print multiple DW01s and expiring items stickers, and when updating a kit</p> <p><strong>Users</strong><br /> all AFEMS users</p>
20136add attachment serial update grid01271WarehouseAF: AFERMSNewSubmitted: 15 Mar 2018<p><strong>Description</strong><br /> when I update certain kits, I need to add an additional form to the kit record. the form needs to stay associated with kit.</p> <p><strong>Recommended</strong><br /> on the "serial kit update" grid add an "add attachment" button. allow multiple attachments, allow deleting old attachments</p> <p><strong>Mission Critical</strong><br /> important</p> <p><strong>Benefits</strong><br /> improves accuracy of data.  prevents keeping a paper file for each item.</p> <p><strong>Users</strong><br /> all</p>
20135kit search parameter01270WarehouseAF: AFERMSNewSubmitted: 15 Mar 2018<p><strong>Description</strong><br /> inventory update mgr shows all my inventory whether it is a kit or not. I have a filter for the "kit" column, but the filters aren't very user friendly</p> <p><strong>Recommended</strong><br /> add "kit?" to the search parameters in the inventory update mgr grid</p> <p><strong>Mission Critical</strong><br /> desirable</p> <p><strong>Benefits</strong><br /> ease of use.</p> <p><strong>Users</strong><br /> all</p>
20134shelf life extension label01269WarehouseAF: AFERMSNewSubmitted: 15 Mar 2018<p><strong>Description</strong><br /> we cannot print shelf life extension labels unless we use the shelf-life extension function.  we cannot use shelf life extension function for serialized extensions or small batch extensions. For these items we use editable expiration date in inventory update mgr.</p> <p><strong>Recommended</strong><br /> add check box to edit grid when changing expiration date to initially print extension label. add button on selected items tab "print extension label" to allow printing a replacement label.</p> <p><strong>Mission Critical</strong><br /> desirable</p> <p><strong>Benefits</strong><br /> eliminates having to manually fill out an item extension label form.</p> <p><strong>Users</strong><br /> all users who extend individual serialized assets.</p>
20133DEPOT Return Date block on PA asset record01268PAAF: VSCOSRemovedSubmitted: 3/27/2018<p><strong>Description</strong><br /> Currently, you cannot annotate the date that an asset has return from DEPOT-Level Maintenance. Annotating the proper date adjusts the assets End of Life cycle.</p> <p><strong>Recommended</strong><br /> Add a date block under the Origl In Svc Dt, labeled DEPOT Return Dt. This is on the Basic tab of the asset record in Property Accountability. See separate word document of example. Also this date should be available at the MNU vehicle asset record/on the Vehicle Characteristic tab.</p> <p><strong>Mission Critical</strong><br /> Yes, this is mission critical. Will show the proper life cycle years, assist with how money is expended for maintenance and when replacements are needed.</p> <p><strong>Benefits</strong><br /> Benefits will improve the accuracy of End of Life Cycle management of assets returning from DEPOT-Level Maintenance.</p> <p><strong>Users</strong><br /> All Air Force fleet managers/maintenance controllers will be effected by this.  </p> <p><strong>27Mar2018 – cancelled per Anthony Sledge </strong> <br /> We need to take another look at our process.</p>
20132ICN Label Management01263WarehouseAF: VSCOSNewSubmitted: 02/27/2018<p><strong>Description</strong><br /> Warehouse needs an ICN Label Manager that will allow users to view/print or reprint ICN labels.</p> <p><strong>Recommended</strong><br /> Create an option on the drop down menu of the Materiel Management tab called ICN Label Manager.</p> <p><strong>Mission Critical</strong><br /> It is not mission critical or mandated but it will enable Warehouse officers/Technicians to manage labels without utilizing the Inventory Update Manager function of the Materiel Mgmt tab.</p> <p><strong>Benefits</strong><br /> Having a centralized location to manage bar codes would save a lot of man-hours and enable better accountability of materiel.</p> <p><strong>Users</strong><br /> This option would benefit all Warehouse users. See attached document for visual explanation.</p>
20131Warehouse Transfer01267WarehouseSPECWARCOMDoneSubmitted: 03/21/2018<p><strong>Description</strong><br /> Streamline 'Warehouse Transfer' process to allow asset selection without first having to enter a stock number. Armory personnel rarely process assets by stock number.</p> <p><strong>Recommended</strong><br /> Modify the current the 'Warehouse Transfer' process to allow the following:</p> <ol> <li>Select assets without having to first enter a stock number (ie... choose assets by location, nomenclature, serial number, etc...)</li> <li>Produce a “Hard Stop” when Gaining Warehouse is not authorized to receive the Stock Number being proposed to be shipped. <br />This will prevent the shipping of an asset to a warehouse that should not have the asset.</li> </ol> <p><strong>Mission Critical</strong><br /> Mission Critical - Due to armory transfer business process mandate.  Transfers must be accomplished in accordance with standards required by OPNAVINST 5530.13C, NAVSEASYSCOMINST 8370.2D and COMNAVSPECWARCOMINST 8020.2A. Assets are selected for transfer based on location, Nomenclature, or serial number.  Serialized assets must only be shipped to a warehouse that is authorized to receive the asset. </p> <p><strong>Benefits</strong><br /> This will allow NSW Armories to maintain their current operational level of support and will ensure shipments from NSW armories to CRANE (and vice versa) are being to shipped to the correct warehouses</p> <p><strong>Users</strong><br /> This will apply to all users within COMNAVSPECWARCOM</p> <p><strong>Completed – Release 6.2 – 31 August 2018</strong></p>
20130Physical Inventory Process01266WarehouseSPECWARCOMDoneSubmitted: 03/21/2018<p><strong>Description</strong><br /> Need to streamline the 'Physical Inventory' process to allow 'adhoc' inventory events and add additional signature fields to existing DPAS produced inventory forms. Inventory forms/reports should contain minimum essential information similar to existing NSW armory inventory forms/reports to allow the maximum number of assets.</p> <p><strong>Recommended</strong><br /> Modify the current 'Physical Inventory' process to allow the following:</p> <ol> <li>Provide ability to generate inventory by serial number in addition to Stock Number, Location, or Inventory Segment Code</li> <li>Prevent the ability to delete serialized assets during the inventory process</li> <li>If a serialized asset is not accounted for during an inventory event, require a method to close out the inventory event and process the discrepancy separately.</li> <li>When inventory events occur using the 'Unit Reconciliation Process, need the ability to inventory select serial numbers (current process is an 'all' or 'none' process)</li> <li>For the inventory forms, need the following signatures blocks added "Inventoried By” and “Verified By”</li> <li>Inventory forms should contain similar information and formatting contained on the current inventory form.</li> </ol> <p><strong>Mission Critical</strong><br /> Mission Critical - Due to Weapons and VAS Accountability mandate. Inventories must be accomplished in accordance with standards required by OPNAVINST 5530.13C, NAVSEASYSCOMINST 8370.2D and COMNAVSPECWARCOMINST 8020.2A. Inventories are required for serialized assets that are deployed, in remote IDTC locations, and in garrison. Inventories are conducted utilizing inventory forms/reports provided by the accountable armory. Inventories must be conducted and documented as quickly as possible to reduce the impact on training and combat operations.</p> <p><strong>Benefits</strong><br /> This will allow NSW Armories to maintain their current operational level of support with minimal impact to the amount of time it takes to perform required monthly inventories</p> <p><strong>Users</strong><br /> This currently applies to Armory users within NSW, but it is foreseeable that it could be applied to other departments within the command at a later date.</p> <p><strong>Completed – Release 6.3 – 21 December 2018</strong></p>
20129Improve Assessment Capability01265WarehouseSPECWARCOMDoneSubmitted: 03/21/2018<p><strong>Description</strong><br /> Need to modify current Armory assessment process so assets that are in a 'issue' status can have assessments performed without the need to have them returned. Also, when 'issued' assets are having an assessment performed, the Armory needs the ability to decrement the repair parts being used during the assessment from the original owning warehouse of the assets (ex... LOGSU2 issues assets to SEAL Team 2, when the assessment is performed on those assets, the repair parts being used will need to decrement from the LOGSU2 O/H repair parts inventory). The NSW Armories need the ability to be able to assess multiple serial numbers (attached to same stock number) at the same time. Lastly, the NSW Armories need an 'Assessment Summary Report' created similar to what their current system provides.</p> <p><strong>Recommended</strong><br /> Modify the current the 'assessment' process to allow the following:</p> <ol> <li>Allow assets in an 'issue' status to be assessed</li> <li>When performing an assessment on issued assets, allow the repair parts to be decremented from the Owning Warehouse from which the asset was issued from.</li> <li>Allow the ability to assess multiple stock numbers at the same and giving the user the ability to replace the same repair part(s) for all serial numbers in that assessment.</li> Create a 'Assessment Summary Report' similar to what their current system provides today. A copy of this report was provided to Leidos. <li>Create an 'Assessment Due' Report similar to what their current system provides today. A copy of this report was provided to Leidos.</li> <li>Create the ability to filter/select data for both reports by commodity, location, assessment due range, nomenclature, or stock number.</li> </ol> <p><strong>Mission Critical</strong><br /> Mission Critical - Due to Maintenance requirement mandate. Maintenance assessments and repairs must be accomplished in accordance with current standards required by NAVSEASYSCOMINST 8370.2D and COMNAVSPECWARCOMINST 8020.2A. Maintenance assessments are required prior to SEAL/SB Team deployment. The IDTC time-line does not allow wholesale asset turn-in for maintenance. Assessments and repairs must be conducted while assets remain in SEAL/SWCC OICs/AOICs custody. Assessment results and repair parts usage must be documented when assets are not in the custody of the accountable armory.</p> <p><strong>Benefits</strong><br /> This will allow NSW Armories to maintain their current operational level of support with minimal impact to the amount of time it takes to perform COMNAVSEASYSCOM and COMNAVSPECWARCOM required armory maintenance actions.</p> <p><strong>Users</strong><br /> This currently applies to Armory users within NSW, but it is foreseeable that it could be applied to other departments within the command at a later date.</p> <p><strong>Partially Completed – Release 6.2 – 31 August 2018</strong></p> <p><strong>Partially Completed – Release 6.3 – 21 December 2018</strong></p> <p><strong>Completed – Release 7.0 – 20 April 2019</strong></p>
20128Improve Unit Issue Process01264WarehouseSPECWARCOMDoneSubmitted: 03/21/2018<p><strong>Description</strong><br /> Need to streamline/improve the current Unit Issue Process. Current process was set up for multiple steps to be used by multiple individuals, whereas COMNAVSPECWARCOM armories typically operate with a single Database Manager processing all issues/receipts/moves/turn-ins.</p> <p><strong>Recommended</strong><br /> Streamline Unit Issue Process, simplify it to allow the following within a single (or very few) processes/screens. Ideally, NSW Armories would like the following streamlined approach to execute a unit issue:</p> <ol style="list-style-type: lower-alpha;"> <li>Select UIC to be issued material</li> <li>Select UIC Custodian (RO)</li> <li>Select assets to be issued (user would like to be able to select assets by location, stock number, nomenclature, or serial number. Need the ability to have a variety of assets selectable by using any one or more of above filtering mechanisms.</li> <li>Choose staging location for assets</li> <li>Submit the issue</li> <li>Print Issue Document for user to sign</li> </ol> <ol> <li>Recommended Solution #1: Combine the 'request' , 'edit header', 'select assets',  'pick plan', 'material movement pick' and 'sign' into a single unified process.</li> <li>Recommended Solution #2: Modify the DW04 form to allow the user the ability to view components of a managed kit or not. Additionally, need the form to accommodate more serial numbers than its current format. A typical NSW Platoon issue will contain roughly 600-800 serial numbers in a single issue.</li> </ol> <p><strong>Mission Critical</strong><br /> Mission Critical - Due to accountability mandate. Unit issues must be accomplished within the current time line in order to support COMNAVSPECWARCOMINST 8020.2A requirements. SEAL/SWCC OICs/AOICs are required to assume custody of all serialized armory assets issued. OIC/AOIC availability is limited due to training and deployment commitments.</p> <p><strong>Benefits</strong><br /> This will allow NSW Armories to maintain their current operational level of support with minimal impact to the amount of time it takes to process a SEAL/SWCC team load-out.</p> <p><strong>Users</strong><br /> Yes, this affects all users within NSW, not just Armory. Many of our departments within NSW operate their issuing processes very similar to the Armory.</p> <p><strong>Completed – Release 6.2 – 31 August 2018</strong></p>
20127Add Segregation Cd to Warehouse and Materiel Mgmt01262WarehouseSOCOMNewSubmitted: 3/21/2018<p><strong>Description</strong><br /> The current DPAS Warehouse and ICP architecture does not provide for the delineation of property beyond Owning DODAAC and Project Cd. <br /> The Project Cd is somewhat controlled by DoD (several restrictions on what is user controlled) and is limited to 3 characters. <br /> The Owning DODAAC is limited to 6 characters and must be a valid DODAAC when routing transactions through DAAS.  <br />USSOCOM, as a Source of Supply is somewhat unique in that it with the Services' Special Forces to determine equipment requirements and in some instances secures funding from the Services to acquire the equipment. <br /> When this occurs USSOCOM requires the capability to "Segregate" the inventory to know how many are allocated to each special force along with what program the materiel/equipment belongs to.  <br /> Reportable Commodity Types will not suffice as the same Stock Nbr exists within multiple programs. <br />  We conferred with EBSO concerning the possibility of expanding the Purpose Code (similar usage, but currently only 1 character),  and the Project Code (3 characters) to prevent adding a new attribute. <br /> That was vetoed stating this would impact all DoD users and possibly the current DLMS to MILS conversion.</p> <p><strong>Recommended</strong><br /> USSOCOM is preparing a DLMS PDC to add a new Industry Cd value to allow for the Segregation of the equipment in inventory. <br /> General concurrence has been given by EBSO for the new Industry Code pending receipt of the PDC and staffing. <br /> USSCOM desires the segregation code to be available for use with all DLMS transactions that flow between ICP and the RSA. <br /> Currently USSOCOM has in excess of 1K Segregation Codes. <br /> The Segregation Cd must be table driven with a user process that is role based to allow for the Add Update and Delete of the values. <br /> The Warehouse and ICP inventories must be Searchable and viewable by Segregation Code. <br /> Screens that are modified to allow for the input/selection of a Segregation Code e.g. Receiving, Update, Issue should provide intellisense as well as a drop-down along with a Browse selector for selecting the correct Segregation Code. <br /> It is recognized that some users of the DPAS application may not want to use the Segregation Code, but USSOCOM believes for its wholesale warehouses it is a must, thus there must be system controls to force the selection of a Segregation Code when applicable. <br /> It is requested that this SCR be developed in concert with the DLMS PDC to ensure the characteristics of the Segregation Code are the same. <br />  Lastly, it is noted that DPAS does not currently have the standard DoD Supply Chain Purpose Code attribute as part of its inventory attributes. <br /> Consideration should be given to adding it as part of this SCR. <br /> Purpose Cd is "Service" defined as will be the Segregation Cd. <br /> The 2 values will mirror each other in functionality, except for it length and actual values. <br /> The benefit of having the Purpose is that all DoD Supply Chain system recognizes the Purpose Cd attribute. <br /> EBSO appears to be planning to limit Segregation Cd to use by USSCOM / DPAS.</p> <p><strong>Mission Critical</strong><br /> Yes - USSOCOM is unable to implement DPAS to manage the inventory in its Lexington warehouse without this change.</p> <p><strong>Benefits</strong><br /> With numerous programs and various sources of funding, this permits USSSOCOM and other users of DPAS to segregate its inventory as they need.</p> <p><strong>Users</strong><br /> This will affect all users of the Warehousing and Materiel Mgmt modules.</p>
20126Additional Physical Inventory Methods01261WarehouseSOCOMNewSubmitted: 3/15/2018<p><strong>Description</strong><br /> A number of the USSOCOM activities are using the DPAS Warehouse module as their APSR for personal property vs. a true Warehouse type operation.  <br />As such, DODI 5000.64 is their guidance for conducting Physical Inventories as opposed to a the traditional DOD Warehouse physical inventory policy found in DOD 4140.1-R.  <br />DODI 5000.64 provides for alternative methods/periods for conducting Physical Inventories other than 100% / year. In addition to 100% Physical Inventories, there is a need to be able to request / conduct Ad Hoc Inventories e.g. Serial Nbr, CIIC, etc., and to be able to plan and conduct a Cyclic Physical Inventory where the system computes a % of the inventory to be conducted / period while ensuring all items have been inventoried within the cyclic period. <br />Consideration should also be given to allowing for the update of the DOLI via  activities where the item would have had to have had a positive siting e.g. Assessment, Inspection, Work Order etc.  <br />Lastly, due to the nature of how the warehouses are being used, there are items within the inventory that do not meet the DODI 5000.64 threshold for accountable property. <br /> The system should provide for a method to exclude certain items from being subject to a Physical Inventory.</p> <p><strong>Recommended</strong><br /> Modify the Physical Inventory process to enable additional methods to conduct and mange Physical Inventories as DODI 5000.64 permits to include Ad Hoc and Cyclic.  <br />Be able to exclude items that are not subject to Property Accountability from having to have a Physical Inventory conducted e.g. unit dollar value of less than $1.<br /> Examples of desired Inventory Reports:</p> <ul> <li>Annual 10% sampling for items with a unit dollar value of > $1 and $5K</li> <li>Annual 100% inventory for items with a unit dollar value > $5K</li> <li>Semi-annual 100% inventory for controlled inventory items</li> </ul> <p><strong>Mission Critical</strong><br /> Mandated per existing business processes and CLS contract at PEO-SOFSA.</p> <p><strong>Benefits</strong><br /> Supports existing contractual requirements for GOCO CTRs.</p> <p><strong>Users</strong><br /> Enhancement affects all users</p>
20125Add Condition Cd to Warehouse ICN Label01260WarehouseSOCOMDoneSubmitted: 3/15/2018<p><strong>Description</strong><br /> There is a requirement to include the "Condition Cd" value on the Inventory Control Nbr (ICN) label that is printed from the DPAS Warehouse Module.  The value should be included on the 2"x3" and 4"x6" label. </p> <p><strong>Recommended</strong><br /> Include "Condition Code" on the ICN Label.</p> <p><strong>Mission Critical</strong><br /> Mandated per NSWC Crane's CAPs and IAW audit findings.</p> <p><strong>Benefits</strong><br /> Mandated per NSWC Crane's policy and audit Corrective Action Plans (IAW audit findings).</p> <p><strong>Users</strong><br /> All users</p> <p><strong>Completed – Release 6.1.2 – 01 Jun 2018</strong></p>
20124ICP and OM&S Depreciation01259WarehouseSOCOMNewSubmitted: 3/15/2018<p><strong>Description</strong><br /> Need GEN PP&E and Military-coded equipment to have the ability to depreciate within the Materiel Management module. Need ability to track and provide financial reporting data of GEN PP&E data in the ICP (Materiel Management Module) as well as OM&S.</p> <p><strong>Recommended</strong><br /> Make the Depreciation key within the catalog a functional data element.</p> <p><strong>Mission Critical</strong><br /> Mandated per DoD 5000.64 and IAW FIAR guidance.</p> <p><strong>Benefits</strong><br /> Allows use of the Warehouse module for financially reporting depreciable GE.</p> <p><strong>Users</strong><br /> All users.</p>
20123FLIPL (Financial Liability Investigation for Property Loss) form DD20001258EnterpriseSOCOMNewSubmitted: 3/7/2018<p><strong>Description</strong><br /> Request Disposition Type FLIPL, so a report can be run to show what assets are in FLIPL processes.</p> <p><strong>Recommended</strong><br /> Under disposition type: L-Local Disposal,  add another Disposition Reason labeled "FLIPL." <br />Objective (FOR NSW) Include the ability for FLIPL form (DD200) to be generated automatically. <br />For NSW, the following is being requested:</p> <ol> <li>Under disposition type: L-Local Disposal, add additional Disposition Reasons labeled:</li> <ul> <li>Beyond Economical Repair (BER)</li> <li>DMIL</li> <li>Expired</li> <li>Destroyed</li> </ul> <li>Add an additional Disposition Type labeled 'SURVEY'. The Disposition Reasons for this Disposition Type would be:</li> <ul> <li>LOST</li> <li>DAMAGED</li> <li>STOLEN</li> <li>DESTROYED</li> </ul> </ol> <p><strong>Mission Critical</strong><br /> Enhancing Feature.</p> <p><strong>Benefits</strong><br /> Improves the accuracy of the data descriptions and reporting of the asset's disposal status. Allows personnel conducting inventories to see that the asset is in FLIPL process. Speeds up inventory process by preventing person conducting inventory from searching for items already identified as a FLIPL (pending loss) </p> <p><strong>Users</strong><br /> All Users</p>
20122Custodian Roles01257PASOCOMDoneSubmitted: 3/20/2018<p><strong>Description</strong><br /> Need an overall custodian role that includes all current custodian roles. Currently there are seven custodian roles that break out various capabilities. Require one over-arching role for custodians since majority take the APO course for the in person training, and then are downgraded to Custodian roles. Users authorized to perform all levels of custodian functions would only need to submit one DPAS Roles request instead of several. </p> <p><strong>Recommended</strong><br /> Establish an overarching Custodian Role (potentially a DPAS Role 1078). This role would roll up all existing Custodian Functions into one role.</p> <p><strong>Mission Critical</strong><br /> Not mission critical, this is an enhancement to the existing DPAS Custodian roles.</p> <p><strong>Benefits</strong><br /> Eliminates the need for Custodians that need to perform all of the various custodian functions to have more than one role assigned. Allows Custodians that require all custodial functions to take a single on line course, and then submit one roles request. </p> <p><strong>Users</strong><br /> Impacts all custodians using the PA Module</p> <p><strong>Completed – Release 6.2 – 31 August 2018</strong></p>
20121Add MRO report to MDR01256WarehouseUSMCDoneSubmitted: 20 Mar 18<p><strong>Description</strong><br /> More and more LOGCOM customers are utilizing DPAS-WM MRO report from the Storage Command LP.  They have requested that the report be added to the daily feed into the Master Data Repository (MDR) for the USMC.  </p> <p><strong>Recommended</strong><br /> Include the DPAS MRO report in the daily MDR feed.  </p> <p><strong>Mission Critical</strong><br /> It is not mandated but it will improve MRO management within LOGCOM. </p> <p><strong>Benefits</strong><br /> We do not have to add a bunch of new DPAS-WM accounts for personnel who will only utilize the MRO report feature of DPAS-WM. </p> <p><strong>Users</strong><br /> This only affects Weapon Systems Management Center (WSMC) and Marine Forces Storage Command (MFSC). </p> <p><strong>Completed – Release 6.2.2 – 21 September 2018</strong></p>
20120Print Multiple DW-01s01255WarehouseAF: AFERMSDoneSubmitted: 15 Mar 2018<p><strong>Description</strong><br /> Currently we have to print multiple DW-01s individually. this takes a lot of time when I have to print all the DW-01s for a set or an NSN. </p> <p><strong>Recommended</strong><br /> set kit outfit, serial update currently allows us to print multiple labels for expiring items.  give us a "DW-01" button that uses the same "print" checkbox as expiring items. almost all the time an expiring items label is printed, a DW-01 is printed. This would save us having to check another column to get the data.</p> <p><strong>Mission Critical</strong><br /> highly desired</p> <p><strong>Benefits</strong><br /> time savings</p> <p><strong>Users</strong><br /> all</p> <p><strong>Completed – Release 6.2 – 31 August 2018</strong></p>
20119Containers inside of Containers01254WarehouseAF: AFERMSNewSubmitted: 15 Mar 2018<p><strong>Description</strong><br /> There is no current ability to place a container inside a container. ISU 90s are shipping, mobility type containers, they have containers in them that have their own inventory checklists. They are removed from the container and dispersed to locations when they arrive at a deployed location.</p> <p><strong>Recommended</strong><br /> Allow us to place multiple containers inside of a container. ensure that we do not lose visibility of the contents of the containers within a container.</p> <p><strong>Mission Critical</strong><br /> Critical, missions dictate the need to deploy required items, and ISUs (Internal Slingable Units) are use to ship assets around the world. </p> <p><strong>Benefits</strong><br /> time savings, accurate location data.</p> <p><strong>Users</strong><br /> all</p>
20118Asset Transactions from iRAPT01253PAOSDDoneSubmitted: 3-7-2018<p><strong>Description</strong><br /> The Department has been struggling with the timely identification of assets being delivered to the Department, thus the initial receipt transaction is not being made in a timely manner.  The current interface between DPAS and IRAPT does not capture all of the transactions because the interface is limited to monitoring the Ship To DoDAAC.  There are many instances where the Ship To organization is not the original purchasing organization.  In these instances, iRAPT does not sent the asset transaction to the purchaser of the asset.</p> <p><strong>Recommended</strong><br /> Identify methods to improve the iRAPT interface to provide all of the transactions for DPAS users.  Several options have been presented but nothing has been proven of tested to determine if they will provide the needed universe of transactions.  The current list of options is:</p> <ol> <li>setup routing in DAAS to provide transactions to DPAS based on additional 'DoDAAC' data elements, such as bill to and approved by.</li> <li>rout transaction from iRAPT based on the Accounting Identifier in the Line of Accounting.</li> <li>retrieve transactions from the newly developed Data Lake</li> </ol> <p><strong>Mission Critical</strong><br /> critical to close audit findings due to delayed processing of the initial receipt of assets</p> <p><strong>Benefits</strong><br /> provides assets to the DPAS community in a timely manner once the vendor indicates the assets are shipped via iRAPT.</p> <p><strong>Users</strong><br /> All</p> <p><strong>Completed – Release 7.0.2 – 17 May 2019</strong></p>
20117Add DoD Serial Number to Custodian Inventory Report01252PANavyNewSubmitted: 2018/02/15<p><strong>Description</strong><br /> DoD Serial Number details not provided in "Custodian Inventory Report."  NAVFAC requires the USN in the serial number field, and VIN in the DOD Serial Number Field. Without VIN in DOD Serial Number Field, accurate verification of VIN against USN on vehicle assets cannot be completed. </p> <p><strong>Recommended</strong><br /> Add DoD Serial Number Field to "Custodian Inventory Reports". This will allow accurate verification of VIN data against USN data on vehicle assets.</p> <p><strong>Mission Critical</strong><br /> No.  This is a matter of improving inventory accuracy. Having the DoD Serial Number Field made available on Custodian Inventory Reports would be extremely beneficial while conducting inventories on vehicle assets.</p> <p><strong>Benefits</strong><br /> Improves inventory accuracy and Reduces Time and Costs.</p> <p><strong>Users</strong><br /> Yes</p>
20116Bulk Serialized Issue01251WarehouseUSMCNewSubmitted: 7 Feb 2018<p><strong>Description</strong><br /> Currently while conducting an Individual or Unit issue there is no way to be able to edit an bulk item being issued and add a Serial Number to that item without having it serially managed in the catalog.  CSP is looking to remove the serialized managed from all E SAPI and Side SAPI plates  and make these items bulk managed, CSP would still need the ability to add a serial number during an Individual or Unit Issue process of a bulk item.  </p> <p><strong>Recommended</strong><br /> Recommend that during the Individual or Unit issue process the clerk will have the ability to be able to edit an item being issued out and add a serial number to that item being issued out, thus still giving us the ability to search by that edit box the serial number that the member was issued.  Also still need the serial number to be viewable on a members issue and outstanding items receipt. </p> <p><strong>Mission Critical</strong><br /> Yes, having this process will help with the accountability and Physical Inventory process of serialized E SAPI and Side SAPI thus saving numerous man-power hours, but still keeping with the mandated policies and procedures sent by below email from Michelle at PM ICE:<br />concur with your plan to capture ESAPI serial numbers upon issue.  From PM ICE perspective, the purpose of serial numbers on ESAPIs is for tracking scanned plates' serviceability and identification of recalled plates.  As long as the NDTE machine is capturing serial numbers of scanned plates and every new plate is scanned -- along with capturing serial numbers of every issued plate, the requirement is met.   Also, NCIS appreciates when the CSP can track a stolen serialized plate to the last known user.  The USMC finds the most practicable approach to comply with PM ICE directives is to warehouse manage the assets as bulk and capture serial numbers upon issue/return.  </p> <p><strong>Benefits</strong><br /> Improve the accountability and Physical Inventory process of serialized ESAPI and SIDE SAPI's thus saving government Numerousness man-hours and costs. </p> <p><strong>Users</strong><br /> All IIF/UIF</p>
20115Add Master Data Appropriation access to 1024 and 1190 roles01250PANAVSUPDoneSubmitted: 2018 February 7<p><b>Description</b><br /> BSO's do not have the functionality to build appropriations (fund codes) within Master Data. In order for BSO's to fully control IUS Construction In Process, DPAS Roles will need to be modified.</p> <p><b>Recommended</b><br /> Recommend (WPUTN34 Appropriation) be added to the Navy PPM Role (DPAS 1024) and Accounting Role (DPAS 1190). The accounting role would allow BSO's to segment out CIP responsibilities within their organizations.</p> <p><b>Mission Critical</b><br /> No. However, with the upcoming requirement for BSO's to manage Capital IUS within the APSR, BSO's will require the ability to manage and monitor costs on all CIP Projects within their claimancy.</p> <p><b>Benefits</b><br /> This change request will save time and improve accountability at the Echelon II level for Capital IUS projects.</p> <p><b>Users</b><br /> This SCR will affect all BSO's who receive and manage CIP and IUS.</p> <p><strong>Completed – Release 6.0 – 27 April 2018</strong></p>
20114Inventory Update Quantity Adjustment01249WarehouseUSMC: DMCNewSubmitted: Feb 06 2018<p><b>Description</b><br /> There is a USMC requirement (Supply Order 4400-201, Chapter 9 and 13) to have a verification step during any quantity adjustments that occur in the DPAS application. Currently the only place that a quantity can be adjusted is in the inventory update manager.</p> <p><b>Recommended</b><br /> Recommend having a pop up that states "Are you sure you want to make this adjustment?" This is a generic enough statement to be used easily across the program, but will also meet the requirements that the Marine Corps requires. This will also reduce the amount of mistakes when adjusting inventory.</p> <p><b>Mission Critical</b><br /> This is mission critical due to the requirements of the Marine Corps to have this verification step.</p> <p><b>Benefits</b><br /> The benefits of implementing this solutions is that it would align all of the USMC Logistics Programs with Marines Corps requirements and the chance of improving inventory accuracy through verification during the quantity adjustment process. </p> <p><b>Users</b><br /> This will affect all users who use the inventory update manager process to make inventory adjustments.</p>
20113GFP/GFM Location01248EnterpriseLeidosDoneSubmitted: February 1, 2018<p><b>Description</b><br /> Current policy requires that the Vendor's CAGE be entered as the Location of GFP/GFM that is has been sent to a contractor for use/repair.  This policy allows any person/auditor conducting an audit to know the vendor to contact to validate that they are in possession of the item being reviewed for existence & completeness.  Currently DPAS does not enforce this policy although the user is able to comply with this policy without a DPAS change.  AT&L PP&E policy office is requesting that DPAS modify it's system to better enforce the policy</p> <p><b>Recommended</b><br /> When performing an issue of GFM/GFP, move the CAGE from the Contractor record that is being associated to the Location field in the screen.  Upon the selection of update, if that CAGE is not currently a valid location, insert a new location record for that UIC using the supplied Vendor's CAGE noting that the location is a "Loaned" Type location (only used for when materiel/equipment is out on loan.  When the materiel/equipment is returned, check to see if this is the only item assigned this location.  If yes, remove the location from the location table.  If no, leave the location in tact.     <br />Note: This requirement needs to be addressed within the Materiel Mgmt / Warehousing modules when GFM/GFP tracking is implemented.  The outcome may be slightly different depending upon whether the organization is using the Materiel Mgmt module.  When the Materiel Mgmt module is used, then the Warehousing module would no longer have this materiel in inventory as it would have been issued.  Tracking may need to be accomplished by establishing a new RSA/C-ICP type.  When the Materiel Mgmt module is not used, then it may be possible to record this materiel as a "Unit Issue", but to a vendor (CAGE and/or DODAAC).The Warehousing / Materiel Mgmt changes may also require the adding of one or more GFM / GFP reports to provide the visibility of GFP/GFM.</p> <p><b>Mission Critical</b><br />This change is being directed by the AT&L PP&E Policy Office.</p> <p><b>Benefits</b><br /> The change will improve overall accountability / visibility of GFM from within specific reports.</p> <p><b>Users</b><br /> Only those organizations with GFM/GFP will require this functionality.</p> <p><strong>Completed – Release 6.3 – 21 December 2018</strong></p>
20112Depreciation Report Rerun01247PADoDEANewSubmitted: 02-02-2018<p><b>Description</b><br /> The Depreciation report can not be generate/run more than once a month.  Adjustments were made to the "Cost" field due to Examination results.  As a result the report is not correct for reporting purposes and month end  closing entries. In order to able to properly record the depreciation and reconcile the system it is necessary to be able to rerun the depreciation report.</p> <p><b>Recommended</b><br /> DPAS system have the capability to natively rerun the depreciation report.</p> <p><b>Mission Critical</b><br /> Not mission critical or mandated but will support FIAR efforts to validate DPAS capital equipment against accounting systems.</p> <p><b>Benefits</b><br /> Improves accuracy in reconciliations and Financial Reporting</p> <p><b>Users</b><br /> Only certain user are affected.</p>
20111DPAS Transfer Function01246PADISANewSubmitted: January 19, 2018<p><strong>Description</strong><br /> DISA investment funding structure requires large volume and dollar value capital asset transfers between its general fund and its working capital fund.  Current DPAS functionality does not generate the needed accounting transactions to support this transfer environment.</p> <p><strong>Recommended</strong><br /> Request DPAS provide a radio button on the CIP Cost update to reflect whether to treat the adjusted cost amount as a “change” or a “transfer out” or “adjustment to a transfer out”.   A change would generate an X819A or M the way the process currently works.  A transfer out will generate an X817A for the difference between the old cost and the new cost.  An adjustment to a transfer out will generate an X817M  (Note: for a transfer out, the new CIP cost must be less than the current cost – an increase to CIP can never be a transfer out. An adjustment to a transfer out must always be an increase to the cost amount.)</p> <p><strong>Mission Critical</strong><br /> Mandated.  DISA is required under the CFO Act of 1990 to generate financial statements that can be audited. This change is required to accurately record the DISA investment funding structure for its capital asset purchases. </p> <p><strong>Benefits</strong><br /> Improves efficiency, accuracy and financial reporting; current practice is a manual process. Process must be performed external to DPAS. Workaround within the DPAS system is not performed.</p> <p><strong>Users</strong><br /> Certain users affected.  DISA has a highly access controlled capital asset structure and procedures, due to the complexity of the capital asset composition and funding and the Departments demands on auditability of the Agency financial statements.</p>
20110Add Attachment During Transfer Process01245PANavyRemovedSubmitted: 1/16/2018<p><strong>Description</strong><br /> Developing an option to "add an attachment" while conducting a transfer in the "Asset Management/Transfer" function.</p> <p><strong>Recommended</strong><br /> Add option to "add attachment" in "Asset Management/Transfer" function.</p> <p><strong>Mission Critical</strong><br /> No.  This is a matter of convenience and time saving.  Transfers are frequent.</p> <p><strong>Benefits</strong><br /> Reduces Time/Cost</p> <p><strong>Users</strong><br /> Yes it impacts all DPAS users.</p> <p><strong>21 Aug 2019 – cancelled per Kevin Callahan </strong> <br /> No Longer Required.</p>
20109Modify DLMS Transaction to support the Product/Service ID Qualifier of "ZZ"01244WarehouseLeidosNewSubmitted: 12/27/2017<p><strong>Description</strong><br /> DPAS is not current compliant with DLMS ADC 295 that was issued on Aug 06, 2008.  DLMS ADC 295 requests all systems that support DLMS transactions to accept a Product/Service ID Qualifier of "ZZ" - Mutually Defined. </p> <p><strong>Recommended</strong><br /> Modify the applicable DLMS transaction processes to accept a Product/Service ID Qualifier of "ZZ".  When a DLMS transaction contains a "ZZ" qualifier, take the Product/Service ID associated with it and check the DPAS Catalog for that value.  The internal business logic would be the same as for Product/Service ID Qualifiers of FS - National Stock Nbr and SW - Stock Number.  Retain the Product/Service ID Qualifier as part of the transaction that is captured in DAPS, and use the Product/Service ID Qualifier of "ZZ" to report back to the submitter where applicable rather than the Product/Service ID Qualifier applicable to the DPAS Catalog record.</p> <p><strong>Mission Critical</strong><br /> Failure to recognize the "ZZ" Product/Service ID Qualifier could result in DLMS transactions being rejected / failed when they shouldn't be / DLMS ADC 295</p> <p><strong>Benefits</strong><br /> Insures DPAS is DLMS compliant, ensure DPAS does not fail or reject a valid transaction.</p> <p><strong>Users</strong><br /> This change would impact any user who has an external DLMS feed from an external ICP or an external Remote Storage Activity (Warehouse).</p>
20108Due-Out / Pending Report Update01243PASOCOMNewSubmitted: 12/13/17<p><strong>Description</strong><br /> Due-Out Inquiry or Pending Transaction Report do not include the Ship To Address info (Activity Name, DODAAC, POC, Address, City, St, ZIP) as well as Phone Nbr, and Email Address.</p> <p><strong>Recommended</strong><br /> To include the fields mentioned above in the Due-Out Inquiry or have the Pending Transaction Report include this data which would be preferred in excel.  I would believe the Due-Out Inquiry would be the preferred method.</p> <p><strong>Mission Critical</strong><br /> With the majority of our transfers being outside DPAS it is critical to be able to track pending dispositions in order to follow up on delinquencies.</p> <p><strong>Benefits</strong><br /> Reduces time/cost and improves accountability.</p> <p><strong>Users</strong><br /> This would benefit all users within our component and agency.</p>
20107iRAPT / DPAS receipt process01242PASOCOMDoneSubmitted: 11/13/2017<p><strong>Description</strong><br /> There is nothing in DPAS that documents that the Property Accountability receipt was the result of a Pending Transaction that was created by a iRAPT (WAWF) transaction.  Today, when an iRAPT receipt is processed through receiving, the "price" is disabled not allowing the user to modify the cost of the item, but once received, the user can modify the cost via Asset Update - Price Change.  The proposed change is to provide an audit trail back to the source of the Receipt (iRAPT). </p> <p><strong>Recommended</strong><br /> Add a column to Asset Master that contains "Key" data from the iRAPT / Warehouse transaction that provides for the necessary audit trail.  This column will be non-editable by the user and would be a data element that the user can view and export to an inquiry/report.  Research of the customer iRAPT 856S transaction set is necessary to determine what attributes should make up the string of data to include in the column e.g Date, Price, Document Nbr, any unique identifiers that will enable an auditor to use this data to retrieve the iRAPT transaction to the Property Accountability / Warehouse receipt.</p> <p><strong>Mission Critical</strong><br /> FIAR compliance is mandated.  This change is considered a necessary feature to improve the audit trail to ensure FIAR compliance.</p> <p><strong>Benefits</strong><br /> Improves the audit trail.</p> <p><strong>Users</strong><br /> All users of iRAPT.</p> <p><strong>Completed – Release 6.0 – 27 April 2018</strong></p>
20106E Catalog01241EnterpriseLeidosDoneSubmitted: 11/3/2017<p><strong>Description</strong><br /> The current architecture for DPAS is 2 master catalogs.  One for Property Accountability and a distinct / separate one for Materiel Mgt/Warehousing.  This requires the customer to manage 2 catalog which is time consuming and prone to error.  There is a need to combine the 2 catalogs into one that is shared between all modules of DPAS.</p> <p><strong>Recommended</strong><br /> Create a process where the customer only has one catalog to maintain and the external National Catalog (FLIS) and Agency specific catalogs (AEMM, TDMS, D043, SOF MDR, C-ICPs, etc.) are integrated as well.  The catalog must be flexible enough to support difference in property between a Property Accountability Organization and a Materiel Mgmt organization (Wholesale vs. Property Book).</p> <p><strong>Mission Critical</strong><br /> To reduce the overall maintenance of the application, the combining of like processes into a single process should accrue savings to the program.</p> <p><strong>Benefits</strong><br /> Reduces the effort required to maintain a catalog, and improves the accuracy of the data as it is only maintained in one place.  It reduces the cost the application maintenance.</p> <p><strong>Users</strong><br /> All users who catalog as well as the Software Development Staff now only one process for managing each Catalog type record.</p> <p><strong>Completed – Release 7.0 – 20 April 2019</strong></p>
20105Warehouse module and PA module have no linkage01240PASOCOMNewSubmitted: 11/2/2017<p><strong>Description</strong><br /> The current DPAS architecture allows for assets to be reflected in the PA and Warehouse modules simultaneously.  This could result in duplicate counting of the asset.  There should be controls in place that prevent the same item (Asset Id, UII, etc.) from being recorded in both modules at the same time unless there is a valid reason (Loan where both the loaner and loanee are DPAS users).</p> <p><strong>Recommended</strong><br /> There should be controls in place to ensure there is no duplication of the same asset.  Issues from the warehouse module should flow through Pending Transactions.  Any receipt or update of key data (PA or Warehouse) should validate that the asset (Stock Nbr / Serial, UII, Asset Id) does not exist in any other accounts whether that account rests within the PA or Warehouse modules as both modules support Property Accountability in addition to assets that may be in warehouse for storage.</p> <p><strong>Mission Critical</strong><br /> This is considered a DPAS design flaw.</p> <p><strong>Benefits</strong><br /> Improves FIAR compliance in that it would ensure an asset is not be recorded in both modules simultaneously.</p> <p><strong>Users</strong><br /> This will impact every user of DPAS as this is requesting validation that the asset does not exist anywhere else in the system.</p>
20104AESIP Catalog Interface01239PAArmyNewSubmitted: 11/3/2017<p><strong>Description</strong><br /> The Army and USSOCOM is requesting that DPAS standardize the Army's data using the Army's Enterprise Materiel Master.  The import of the AEMM will provide for a complete list of attributes associated with a Stock Nbr, not just SB700-20 attributes - current Army Catalog import.  The solution must support Mfr Part Nbr Stock Nbrs that are > 15 characters.</p> <p><strong>Recommended</strong><br /> Create a process that will utilize the Army's AEMM Web Service to retrieve catalog data.  To ensure compliance, there must be methods within the application that prevents the Army user of the AEMM to not be able to create MCNs, Mfr Part Nbr, or be able to catalog an NSN Stock Nbr that does not exist in the AEMM.  For USSOCOM Catalogers, they need to be able to catalogs items that may not be in the AEMM and for USSOCOM, their catalogers must be able to utilize not only the AEMM Agency Catalog, but also their SOF MDR Catalog simultaneously. </p> <p><strong>Mission Critical</strong><br /> Yes.  Army desires Total Asset Visibility within AESIP with all items being known by Stock Nbr / Nomenclature from the AEMM.</p> <p><strong>Benefits</strong><br /> Reduces the effort required to maintain catalog data, ensures common cataloging throughout the Army.</p> <p><strong>Users</strong><br /> Currently it is believed that the AEMM interface is limited to Army and USSOCOM users.</p>
20103No Authorization linkage only manual process/SOLMAN01238PASOCOMNewSubmitted: 11/2/2017<p><strong>Description</strong><br /> The USSOCOM's SOF MDR has Authorization data for the SOCs and TSOCs.  This information is need by DPAS to allow the Units to know what they are authorized / required to what they have on hand, and to be able to validate requisitions.  The goal would be to create an Import and and associate the data with the Unit.</p> <p><strong>Recommended</strong><br /> Have SOF MDR present the data to DPAS.  DPAS would import the data and make it available to the Property Accountability Module's Authorization process, to the Warehouse's Authorization process and to the Materiel Mgmt's Customer Requisition process to assist in determining the validity of the requisition. </p> <p><strong>Mission Critical</strong><br /> Improve / automate authorizations for the SOCs/TSOCs using DPAS.  Provide for validation of the Customer Requisition process.  Without this data being available within DPAS, this process is all manual and is thus subject to the data being inaccurate.</p> <p><strong>Benefits</strong><br /> Reduces the effort required to maintain authorization data.  Improves the validation of a customer Requisition.</p> <p><strong>Users</strong><br /> SOCs, TSOCs, and USSOCOM's Program Managers that are validating a customer requisition.</p>
20102Adding an asset does not query the registry01237MUSOCOMDoneSubmitted: 11/2/2017<p><strong>Description</strong><br /> DPAS does not permit the user to enter a UII in Asset Receiving.  The only way for DPAS to capture the UII is via a iRAPT transaction, DPAS HandHeld UII Assoc, or searching the IUID registry and associating it to the asset.</p> <p><strong>Recommended</strong><br /> Modify Asset Receiving and Asset Update to allow the input of the UII.  Any UII entered should be validated to the registry as a valid UII.</p> <p><strong>Mission Critical</strong><br /> Currently DoD IUID policy requires all assets that are subject to Property Accountability to have a UII.</p> <p><strong>Benefits</strong><br /> Reduces the effort required to associate a UII when it is not inserted via an iRAPT or Handheld process. </p> <p><strong>Users</strong><br /> All users of the PA module could use this feature.</p> <p><strong>Completed – Release 6.2 – 31 August 2018</strong></p>
20101Data Conversion Enhancements01236EnterpriseLeidosNewSubmitted: 11/3/2017<p><strong>Description</strong><br /> DPAS does not permit the user to import data as part of their converting to DPAS.  Today, the user must complete Excel Spreadsheets and submit them to their DPAS Fielding Support team which reviews them for completeness, then forwards them to a DBA for processing.  The goal would be to provide the user with an Import feature within all processes.  This import feature would work similarly to the existing DPAS Member Profile (Warehouse) and the Fuel / Utilization Import (Maint/Util). </p> <p><strong>Recommended</strong><br /> Allow the user to export a template for a specific process, complete it, then import it.  The system would validate the import and add all valid records to the system.  All failed records would be available for export for correction, and / or there would be a "Pending" button that the user could pull up each record that failed validation to be corrected within the Add Screen which would then allow the record to be processed.</p> <p><strong>Mission Critical</strong><br /> Currently the New User Fielding process is needed to support all new Customers converting to DPAS.  By providing a change is how it is accomplished will reduce the customer wait time and allow them to be in more control of when the data is actually loaded.</p> <p><strong>Benefits</strong><br /> Reduces the effort required to convert a new customer to DPAS. Provides greater capability to existing customers that may have a large import to perform.  Can be accomplished without Helpdesk and DBA support.</p> <p><strong>Users</strong><br /> All users of the PA, Warehousing, Materiel Mgmt, and Main/Util modules could use this feature as it becomes available.</p>
20100DPAS Tablet/Phone App01235EnterpriseLeidosDoneSubmitted: 11/3/2017<p><strong>Description</strong><br /> As the Android/Apple IOS platforms become more mainstream in the Department of Defense, there is a need for DPAS to upgrade it's handheld processing features to include these platforms.  These platforms may even replace the Windows Handheld platforms that DPAS currently has in use to perform receipt / QC and Physical Inventory functions in the future.</p> <p><strong>Recommended</strong><br /> Develop the capabilities to export Work Orders for completion on a tablet style device.  Today many service technicians show up at the customer site with the Work Order that is to be completed on an appliance in the home (Washer, Dryer, Refrigerator) and for mechanicals in a home such as (A/C, Heating, Electrical).   Given the state of the WM 6.5 platform, it may be necessary to port the existing DPAS handheld capabilities first.</p> <p><strong>Mission Critical</strong><br /> The immediate need/requirement is to ensure DPAS does not lose the capability to conduct Physical Inventories in an untethered / non-network mode.  DoD has issued noticed that the WM 6.5 Framework will no longer be able to be connected to the DOD Network as of July 2018.  This is an extension from the July 2017 original deadline. </p> <p><strong>Benefits</strong><br /> Provides capabilities for the DPAS user to perform Logistics functions without having to be directly connected to DPAS. A lot of the Logistics functions associated with DPAS are not in the area where the actual work is being performed.  Thus, often times they must write down the data and take it back to the office where it must be typed into a terminal.  The retyping increases cost and increases the risk of error.  The Android/Apple IOS platforms tend to be less expensive that the existing WM 6.5 models, thus delivering DPAS detached capabilities to these style devices will reduce operational costs for the Department.</p> <p><strong>Users</strong><br /> All User of DPAS perform these functions that are currently available on the handheld.  Organizations that are small, may choose to perform some of the functions manually, and may not adopt the latest technology even though it could improve their business practices / reduce the cost of performing those functions.</p> <p><strong>Completed – Release 7.0 – 20 April 2019</strong></p>
20099Inventory Update Quantity Adjustment01234WarehouseUSMC: CSPNewSubmitted: Dec 13 2017<p><strong>Description</strong><br /> There is a USMC requirement (Supply Order 4400-201, Chapter 9 and 13) to have a verification step during any quantity adjustments that occur in the DPAS application. Currently the only place that a quantity can be adjusted is in the inventory update manager.</p> <p><strong>Recommended</strong><br /> Recommend having a pop up that states "Are you sure you want to make this adjustment?" This is a generic enough statement to be used easily across the program, but will also meet the requirements that the Marine Corps requires. This will also reduce the amount of mistakes when adjusting inventory.</p> <p><strong>Mission Critical</strong><br /> This is mission critical due to the requirements of the Marine Corps to have this verification step.</p> <p><strong>Benefits</strong><br /> The benefits of implementing this solutions is that it would align all of the USMC Logistics Programs with Marines Corps requirements and the chance of improving inventory accuracy through verification during the quantity adjustment process. </p> <p><strong>Users</strong><br /> This will affect all users who use the inventory update manager process to make inventory adjustments.</p>
20098Add Asset Id Info to Warehouse Grids01233WarehouseAF: VSCOSDoneSubmitted: 12/07/2017<p><strong>Description</strong><br /> Vehicle Management Material controls require to orders 90 percent of all parts against an asset. Currently, Warehouse does not offer asset id visibility in any of the grids.</p> <p><strong>Recommended</strong><br /> We would like to request Asset ID information to be added to the Maintenance Issue Grid, Warehouse Replenishment Grid, Warehouse Replenishment Approval screen, Due-In Message of the Day screen, and the Material Mgmt Accept/Receive process.</p> <p><strong>Mission Critical</strong><br /> Not mandated but critical.  Air Force Material Control sections need a very detailed process to track, account and issue vehicle parts, equipment and tools against specific Assets to track expenditures and control budgets.</p> <p><strong>Benefits</strong><br /> Adding Asset Id information to the above grids will enable material control sections to improve order and inventory management by enabling warehouse technicians and managers to have direct access to this critical information. Asset Id information allows managers to approve or disapprove requisitions based on priorities assigned to those assets. Asset Id information is also used to track orders/requisitions and it is used to capture and calculate Non Mission Capable Supply (NMCS) as well as Deferred maintenance.</p> <p><strong>Users</strong><br /> All Material controllers Air Force wide will benefit form the addition of Asset Id information to the grids above. This will enhance parts tracking and management which in turn will improve inventory management and cut costs related to miss-assigned parts and erroneous orders.</p> <p><strong>Completed – Release 6.0 – 27 April 2018</strong></p>
20097Add 2 Fields Under Asset Management01232PAMDARemovedSubmitted: 29 Nov 2017<p><strong>Description</strong><br /> Background: On October 20, 2017 the DPAS/DAI interface for 12 Capitalization of Purchased Assets (X819) were identified on the DAI Unhandled Report due incomplete information from DPAS.  The reason the 12 transactions were in the DAI unhandled report was due to  blank fields: BUDGET_FISCAL_YEAR, BA_BSA_BLI, DAI_PROJECT_NUMBER, and DAI_TASK_NUMBER.  The root problem was due to blank information in DPAS two fields (1) Task Cd (DAI Project Number) and (2) Job Order Nbr (DAI Task) in Asset Management; therefore,  interfaced to DAI as blank information.</p> <p><strong>Recommended</strong><br /> Make (1) Task Cd (DAI Project Number) and (2) Job Order Nbr (DAI Task) mandatory fields, this will fix the transactions due to incomplete information. </p> <p><strong>Mission Critical</strong><br /> Mission Critical.  Reporting of incomplete financial data to the general ledger can give a false narrative of the data provided and could cause major issue for financial audit of the Agency Capital Assets.</p> <p><strong>Benefits</strong><br /> By making the two fields REQUIRED in DPAS, (1) Task Cd (DAI Project Number) and (2) Job Order Nbr (DAI Task), it will the eliminate and correct the process in both DPAS and DAI.</p> <p><strong>Users</strong><br /> This will affect all Property Accountability users of DPAS.</p> <p><strong>04Dec2017 – removed per Randy Reed </strong> <br /> Recreating this SCR as a bug.</p>
20096Change Legacy Asset Y1 Fund Code to DAI Interface Fund Codes01231PAMDARemovedSubmitted: 29 Nov 2017<p><strong>Description</strong><br /> There are  an estimated 1,865 legacy assets in DPAS with the default fund code of 'Y1'.  In 2016, new acquired assets were established with fund code procedure that allows DPAS and DAI interface; therefore, the property system of record, DPAS, transfers information to the MDA financial system of record, DAI.   </p> <p><strong>Recommended</strong><br /> Change all Legacy Capital Assets with Y1 as the default Fund Code to reflect fund codes submitted by CPO.</p> <p><strong>Mission Critical</strong><br /> Mission Critical.  At this time, with the amount of legacy assets in DPAS not in DAI, this remains a significant audit risk and finding that needs to be corrected.</p> <p><strong>Benefits</strong><br /> By allowing the CCA to receive a DPAS flat file of the legacy fund codes, CCA can process only one manual JV (versus thousands)  and provide a corrected file to DPAS to update the legacy fund codes.  This will not require CPO to manual update the estimated 1,865 legacy assets in DPAS; therefore, saving an estimated 3,000 man-hours.</p> <p><strong>Users</strong><br /> This will affect all Property Accountability users of DPAS.</p> <p><strong>05Dec2017 – removed per Ryan Steele </strong> <br /> Recreating this SCR as a bug.</p>
20095Add drop-down for OM&S Improvement Cost01230PAMDANewSubmitted: 28 Nov 2017<p><strong>Description</strong><br /> Currently, DPAS - Asset code "O" for OM&S does not allow improvement costs to be added. </p> <p><strong>Recommended</strong><br /> Update system to allow improvement cost to OM&S assets, currently there is no way to add improvement cost to OM&S. DPAS - Asset code "O" code for OM&S does not allow multiple lines of accounting.  The multiple lines allow improvement costs to be added.  MDA Capital assets are funded by multiple lines of accounting; therefore, creating interface issues between DPAS and DAI.</p> <p><strong>Mission Critical</strong><br /> Yes: DPAS - Asset code "O" code for OM&S does not allow multiple lines of accounting.  The multiple lines allow improvement costs to be added.  MDA Capital assets are funded by multiple lines of accounting; therefore, creating interface issues between DPAS and DAI.</p> <p><strong>Benefits</strong><br /> Benefit:  Once the DPAS - Asset code "O" code for OM&S has the ability to have the improvement tab, which allows multiple lines of accounting,  will discontinue interface issues between DPAS and DAI concerning Asset code "O" for OM&S does and improvement costs to be added . </p> <p><strong>Users</strong><br /> This will affect all Property Accountability users of DPAS.</p>
20094Individual Issue Verify All Button01229WarehouseAF: VSCOSNewSubmitted: 11/28/2017<p><strong>Description</strong><br /> Component verification during issue and return processes is too long. Add a 'Verify All' button to the verification process to provide option to verify all items at once.</p> <p><strong>Recommended</strong><br /> Add a 'Verify All' button to the verification process to provide option to verify all items at once. Current process ties up excessive amount of man-hours if item being issued is a kit that contains hundreds of items. This process needs to be accelerated and the addition of a 'Verify All' button will alleviate this issue.</p> <p><strong>Mission Critical</strong><br /> Non-mission critical nor mandated but current process will hinder technician overall productivity by utilizing excessive man-hours in one single process.</p> <p><strong>Benefits</strong><br /> This will exponentially reduce time and improve personnel productivity.</p> <p><strong>Users</strong><br /> This improvement will benefit all users across all services currently using Warehouse.</p>
20093Inactive/Removed User Report00598WarehouseDFAS ColumbusDoneSubmitted: 11/7/2013<p><strong>Description</strong><br /> This change is being requested for the DPAS Warehouse. In accordance with FISMA control IAAC-1. We need the ability to see inactive/cancelled user accounts.</p> <p><strong>Recommended</strong><br /> On the PA side this report is automatically generated overnight. The fields include: User Name, User Id, Estbd Dt, Last Login Dt, Last Site Accessed (this will need changed to Last Warehouse Accessed), Email Address, Phone Nbr & History Remarks. When the user is inactivated or cancelled the History Remarks on the user record is updated with the appropriate action completed. For example Inactivated 30-44 days Inactive; email sent to user. A report from the Property Accountability side is being included with the SCR. <br />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.</p> <p><strong>Mission Critical</strong><br /> This is required to be in compliance with the control.</p> <p><strong>Benefits</strong><br /> The ability to take the item off of the POA&M.</p> <p><strong>Users</strong><br /> No, this will only be used by the DPAS Account Management and anyone assigned to the Admin role.</p> <p>SCR is duplicate of <a href="index.php/support/system-change-request/details/4/13701/inactive-user-reports-pa" rel="alternate">00505</a></p>
20092History Inquiries00776EnterpriseDFAS ColumbusDoneSubmitted: 2/6/15<p><strong>Description</strong><br /> We need to generate history transaction reports for Account Management, users and system generated in-activations and deletes. These items must be reviewed by the Information System Security Manager. This will ensure we are in compliance with the DIACAP control ECTP-1 and NIST Publication 800-53 AC-6-Least privilege.</p> <p><strong>Recommended</strong><br /> Develop history reports to capture any account related transactions. On the PA side the following history reports are being used:</p> <ol> <li>Deleted User History – This shows every user that has been deleted by Account Manager or the system when the account reached 45 days of inactivity. – The fields on this report are:</li> <ul> <li>DPAS User Id,</li> <li>User First Name,</li> <li>User Last Name,</li> <li>Agency Cd,</li> <li>Agency Name,</li> <li>Site-Id,</li> <li>Last Updated By,</li> <li>Last Tran Dt,</li> <li>History Remarks</li> </ul> <li>User Actbl UIC History could be replaced with User Region History. – This shows every user’s Actbl UIC access that was added, updated or deleted by Account Management or by the system when the account was deleted at 45 days of inactivity. – The fields on this report are:</li> <ul> <li>User Id,</li> <li>First Name,</li> <li>Last Name,</li> <li>Site-Id,</li> <li>Actbl UC,</li> <li>Tran Cd,</li> <li>Last Updated By,</li> <li>Start Date,</li> <li>History Remarks</li> </ul> <li>Users History – The results for this inquiry are very large. We need filters to remove some of the unwanted results. – The fields on this report are:</li> <ul> <li>User Id,</li> <li>First Name,</li> <li>Last Name,</li> <li>Site-Id,</li> <li>Tran Cd,</li> <li>Status Cd,</li> <li>Status,</li> <li>Last Updtd By,</li> <li>Last Tran Dt</li> <li>History Remarks</li> </ul> The report shows: <ul> <li>Every normal login made by the user.</li> <li>Every account created or updated by Account Management.</li> <li>All normal user logins.</li> <li>Every time a user changes Site-Id and Actbl UICs.</li> <li>The system generated email sent at 15 days of inactivity.</li> <li>The system generated emails sent to every user at 30 days of inactivity.</li> <li>The system generated email sent at 45 days when the account is deleted.</li> </ul> <li>User Property Custodian History – This shows every Account Management add, update and delete. When a user’s UIC is deleted by Account Management it shows every system delete transaction for each custodians being deleted from that user’s account. It also shows if a custodian is added, deleted or modified by any user on the application. This also is a very large inquiry and filters are needed to reduce the data results. – The fields on this inquiry are:</li> <ul> <li>User Id,</li> <li>First Name,</li> <li>Last Name,</li> <li>Site-id,</li> <li>UIC,</li> <li>Custodian Nbr,</li> <li>Sub Custodian Nbr,</li> <li>Tran Cd,</li> <li>Last Updated By,</li> <li>Start Date,</li> <li>History Remarks.</li> </ul> <li>User Role History – This shows every role added, updated or deleted from the users account. This shows the system deleted the account at 45 days of inactivity. A 2nd email is sent cancelling the user. I’m not sure what the difference is between system deletes and system canceled but it includes both. – The fields on this inquiry are:</li> <ul> <li>User Id,</li> <li>First Name,</li> <li>Last Name,</li> <li>Site-Id,</li> <li>Role Name,</li> <li>Tran Cd, Status,</li> <li>Last Updated By,</li> <li>Start Date,</li> <li>History Remarks.</li> </ul> <li>User Site History – This shows every normal login. This shows every time a user switches a Site-Id or Actbl UIC. This shows every site added, updated or deleted by DPAS Account Management. It shows when an account is cancelled and the email sent. – The fields on this inquiry are:</li> <ul> <li>User Id,</li> <li>First Name,</li> <li>Last Name,</li> <li>Site-Id,</li> <li>Tran Cd,</li> <li>Site Last Login Dt,</li> <li>Last Updated By,</li> <li>Start Date</li> <li>History Remarks.</li> </ul> <li>Users UIC History – This shows every UIC added, updated or deleted by DPAS Account Management. It also shows the systems deletes and the system cancellations. It also shows every UIC added or deleted by a user. – The fields on the inquiry are:</li> <ul> <li>User Id,</li> <li>First Name,</li> <li>Last Name,</li> <li>Site-Id,</li> <li>Actbl UIC,</li> <li>UIC,</li> <li>Tran Cd,</li> <li>Last Updtd By,</li> <li>Start Date</li> <li>History Remarks.</li> </ul> </ol> <p><strong>Mission Critical</strong><br /> Yes, it is required to pass the upcoming SSAE 16 audit in June.</p> <p><strong>Benefits</strong><br /> We will be able to provide the appropriate information for the audit.</p> <p><strong>Users</strong><br /> This SCR is to be incompliance of required controls so we can pass the SSAE 16 audit.</p> <p><strong>Completed - Release 3.0.01 - 02 June 2015</strong></p>
20091Mechanic Role00749MUOSDDoneSubmitted: 1/20/2015<p><strong>Description</strong><br /> USAF desires M&U Role for its Mechanics which will allow them to input time per Sub-Work Order (Job). The Role would have the basic concept of Custodian in PA. The Mechanic would only have access to Sub-Works assigned with limited functionality.</p> <p><strong>Recommended</strong><br /> Create Mechanic Role as outlined in Attachment</p> <p><strong>Mission Critical</strong><br /> No</p> <p><strong>Benefits</strong><br /> For National Guard and Reserve units with reduced manning, this will assist with improved accuracy of direct time and reduce the time to close opened Work Orders.</p> <p><strong>Users</strong><br /> Maintenance Activity Mechanics</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20090USAF-Email Customer00717MUOSDDoneSubmitted: 24Nov2014<p><strong>Description</strong><br /> Email customer of vehicle for pick-up when Work Order is closed.</p> <p><strong>Recommended</strong><br /> Utilize the Customer E-mail information recorded in the M&U>Maintenance>Work Order>Customer tab to send the initial email when the Work Order Status Cd is C-Closed for vehicle.</p> <p><strong>Mission Critical</strong><br /> Improves material readiness by contacting customer immediately upon completion of all work and Work Order is Closed to reduce time available assets in not dispatched.</p> <p><strong>Benefits</strong><br /> Reduces unavailable time between WO close and customer pick-up.</p> <p><strong>Users</strong><br /> M&U Officers and Specialist</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20089After Maint QC failure Open WO00712MUUSMC: DMCDoneSubmitted: 24 November 2014<p><strong>Description</strong><br /> There is no way to see an after maintenance QC Failure any way other than just as an open work order. These technician failures have a higher priority than a normal open work order.</p> <p><strong>Recommended</strong><br /> There has to be some way to flag any after maintenance failures coming back to M&U to allow Maintenance Supervisor to be able to reassign tech to W/O. As stated above, these carry priority over a normal new work order. Suggested solution could be a "select a field" as used with DPAS warehouse module for Grid Option feature.</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> This will reduce time/cost and will ensure accuracy.</p> <p><strong>Users</strong><br /> M&U users will be affected.</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20088Add to grid line condition code, location & WO reason to search criteria00711MUUSMC: DMCDoneSubmitted: 24 November 2014<p><strong>Description</strong><br /> While searching for work orders through "Maintenance/Work Order" method, all pertinent information to the DMC's business processes is not available. We have to see Work Order Reason, Condition Code and Current Location on the main grid line during the work order search process. Due to the fact of Work Orders being removed from the Open Action Folders, it is very difficult to locate and assign work orders. There have been defects written and resolved adding pertinent information to the open action grid line that make it possible to find and assign specific work orders. Now that they have been removed, information needed to locate and assign specific W/Os to technicians is not there.</p> <p><strong>Recommended</strong><br /> These fields have to be added to the grid line just as defect #54 added them to the "Open Action Grid Line". We have to have condition code and location added to the search criteria along with work order reason. Suggested solution could be a "select a field" as used with DPAS warehouse module for Grid Option features.</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> This will reduce time/cost and will ensure accuracy.</p> <p><strong>Users</strong><br /> M&U users will be affected.</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20087Mass update W/O can't add techs nor labor hr00710MUUSMC: DMCDoneSubmitted: 10/23/14<p><strong>Description</strong><br /> When trying to mass update Work Orders in M&U, I discovered there is no way to add Technicians or their labor hours to the Work Order while mass updating Work Orders. You can only assign a single Primary tech while mass updating W/Os. There has to be a way to assign multiple technicians and their labor hours to a W/O.</p> <p><strong>Recommended</strong><br /> Maintenance Officer should be able to assign multiple technicians to a single W/O in the mass update process. There is currently no option to add any tech other than the Primary Tech. To make the Mass Update function work for the DMC business process, there has to be a way to add multiple techs and their labor hours while updating W/Os in mass.</p> <p><strong>Mission Critical</strong><br /> Yes.</p> <p><strong>Benefits</strong><br /> The benefit is that functions will be more role specific an eliminate potential breaches.</p> <p><strong>Users</strong><br /> All</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20086Maint Tech/Supervisor has same capabilities00709MUUSMC: DMCDoneSubmitted: 10/22/14<p><strong>Description</strong><br /> During role specific testing, we found that a Maintenance Specialist (Technician) has all of the same capabilities within the Work Order Process that a Maintenance Officer (Supervisor) does. This means that a technician can edit the W/O in any way, (e.g. - Change level of preservation, change C/C of asset, change priority of W/O, reassign to another tech, etc.) This creates potential for numerous problems.</p> <p><strong>Recommended</strong><br /> There has to be a level of security put in place to limit the technicians capabilities within the W/O process. A technician should only be able to edit fields that are directly related to him/her completing assigned work and updating W/O to reflect this completion.</p> <p><strong>Mission Critical</strong><br /> Yes. The lack of security layers create a potential breach for misuse and improper management.</p> <p><strong>Benefits</strong><br /> The benefit is that functions will be more role specific an eliminate potential breaches.</p> <p><strong>Users</strong><br /> All</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20085Remove QC and NID from M&U W/O00676MUUSMC: DMCDoneSubmitted: 30 June 2014<p><strong>Description</strong><br /> When updating a COSIS W/O with a status code of pending close and a state code of completed awaiting inspection, an error is received stating that a inspection status code is mandatory. This is not done in maintenance.</p> <p><strong>Recommended</strong><br /> The accepted or rejected status happens in Quality Control. This needs to be removed from M&U.</p> <p><strong>Mission Critical</strong><br /> Yes. These are mandatory fields for the M&U personnel but are not M&U functions.</p> <p><strong>Benefits</strong><br /> By implementing this change, the Maintenance supervisor will be able to update work orders with a pending, completed awaiting inspection status.</p> <p><strong>Users</strong><br /> All</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20084Mass update of WO - COSIS Work Plans Incorrectly Require Inspection Fields00708MUUSMC: DMCDoneSubmitted: 24 November 2014<p><strong>Description</strong><br /> When trying to mass update work orders, I receive an error message stating that "Next Inspection Date" and "Inspection Status Code" are required.</p> <p><strong>Recommended</strong><br /> These two requirements are not maintenance functions. They are QC functions and cannot be mandatory fields for maintenance personnel input. This prevents maintenance personnel from being able to mass update work orders with a State Code of "Pending Close" and a Status Code of "Completed Awaiting Inspection". These State codes and Status codes are necessary to send work back to QC for after maintenance inspection.</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> The elimination of these requirements, which are not a M&U function, would reduce time and improve accuracy by not having to put "false" data just to fill in the blank. DELETION of these fields "Next Inspection Date" and "Inspection Status Code" for M&U is a necessity.</p> <p><strong>Users</strong><br /> This affects all users of M&U Module.</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20083QC Direction for After Maint. inspections00705MUUSMC: DMCDoneSubmitted: 6/23/2014<p><strong>Description</strong><br /> On AFTER MAINTENANCE QC Inspections, the inspector has no information directing them on what they should be inspecting for. (i.e. level of preservation, level of prep for ship, repairs made, services performed, etc.)</p> <p><strong>Recommended</strong><br /> The QC Inspector has to have direction telling them what maintenance was performed on asset to be inspected. This will apply to all “After Maintenance” inspections. A field needs to be added reflecting services performed by maintenance. This field would be populated based off of the instructions on the BEFORE Maintenance work order.</p> <p><strong>Mission Critical</strong><br /> Yes. The QC Inspector has to have direction telling them what maintenance was performed on asset to be inspected.</p> <p><strong>Benefits</strong><br /> Enable QC to perform their after maintenance inspections.</p> <p><strong>Users</strong><br /> All</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20082Add drop down State Cd of “Approved Awaiting Transportation"00704MUUSMC: DMCDoneSubmitted: 4/18/14<p><strong>Description</strong><br /> While reviewing the system to assess the fit of the DPAS M&U Module to the DMC Business process, the DMC was unable to tell when transportation completes a move request to deliver the item to its maintenance/repair location within the system. In addition, the location data does not populate in the M&U Module with the location of an asset.</p> <p><strong>Recommended</strong><br /> Within the M&U Work Order, it is requested that DPAS add the State Cd of “Approved Awaiting Transportation” to the drop down menu. It is also requested that when the status of a WO is “Approved Awaiting Transportation” that the maintenance movement screen automatically open to prompt for the user to input the specific location to move assets to when the WO is updated. Once the item is delivered to the maintenance facility, it is requested that DPAS M&U update the location on the WO, and change the stats of the WO to reflect that the item is ready for maintenance to be started (Change of status and “bucket” within the DPAS Work order screen). This will trigger the M&U Supervisor to continue to the next step in the process.</p> <p><strong>Mission Critical</strong><br /> Yes. Due to the lack of notification it causes a delay and work to be done sits idle .</p> <p><strong>Benefits</strong><br /> The benefit is that the tasks or work to be done will be efficiently communicated.</p> <p><strong>Users</strong><br /> All</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20081Custom View does not save fields selected00702MUUSMC: DMCDoneSubmitted: 24 November 2014<p><strong>Description</strong><br /> During the DMC Business Process Fit Assessment, it was discovered that although custom search fields can be selected to create a custom view for the user, the user must select their custom search each time they enter screen. This is a minor annoyance; however, it is a step that will have to be taken each time the user enters the process.</p> <p><strong>Recommended</strong><br /> The DMC is requesting that when a Custom View is created within the M&U Module, that the M&U Module allows for that custom view to be set as the default view for the user. Each time the user logs the default view should be what is displayed, unless the user deletes their default view or changes it. It is desired that this look and feel similar to what the DPAS Warehouse Module is doing for custom & default views within each process/screen.</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> This process improvement would reduce time/cost and improve accuracy since the custom view has already been selected at a previous time.</p> <p><strong>Users</strong><br /> Anyone who uses Custom View will benefit with the ability to save what is first selected.</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20080Catalog Update (Colloquial Name, Catalog TAMCN, IDN)00683WarehouseUSMC: CSPDoneSubmitted: 6 Aug 2014<p><strong>Description</strong><br /> DPAS overwrites the TAMCN Description and Item Description for NSN items. As a result, the CSP Program has all NSN's flagged as Part Numbers due to the fact they have manipulated/changed Item Description names to better match what the item actually is. This is preventing automatic catalog updates, and creates false reports in the system. DPAS was designed around size category being driven by TAMCN. Our system catalog does not provide a TAMCN for all items, and the way we asked DPAS to design that process was incorrect. It is very important to the longevity and sustainment of our program. Currently, the only way we can get the system to work is to set all stock numbers to part numbers.</p> <p><strong>Recommended</strong><br /> For the CSP Enterprise Program, MARFORLOGCOM is requesting to add the following fields to the DPAS Stock Number Table:</p> <ul> <li>Colloquial Name: <br /> The CSP Program has all NSN's flagged as Part Numbers due to the fact they have manipulated/changed Item Description names to better match what the item actually is. With a 'Colloquial Name' field the CSP Enterprise program could use this field for the Item Description and then allow the I-001 interface from MARCORLOGCOM's Tech Data Management System update daily. This will better support audibility once the NSN's have their flag changed from Part Number to NSN managed items. Should this change be accepted, please update Item Description to be a non-editable field within the system for NSN coming from the Agency Catalog. This field must perpetuate through all of the reports and grids options (processes) that contain asset information within the system.</li> <li>Catalog TAMCN: <br /> Another reason that all NSN’s were set to part numbers is because our agency catalog does not have a TAMCN for all items. As a result, the interface for our agency catalog overwrites the TAMCN, when a TAMCN is needed for the individual issue process within the system. This field will be used to represent the Official TAMCN assigned from the Agency Catalog for all NSN’s within the system. This field must perpetuate through all of the reports and grids options (processes) that contain asset information within the system.</li> <li>ID Number: <br /> ID Number is a unique identifier of different variants of items under a TAMCN. It is requested to add this field to the DPAS Stock Number Table and all associated reports and grid options (processes) in the system to support user identification of the different variants of an asset.</li> </ul> <p>Applying these two changes to the system will better support audibility, as it will allow the CSP to change the NSN’s they have flagged as Part Number Managed to NSN managed items.</p> <p><strong>Mission Critical</strong><br /> This is a policy mandated system change, that will allow the CSP data to be reported IAW Marine Corps Cataloging Policy.</p> <p><strong>Benefits</strong><br /> Improves accuracy and accountability with respect to catalog data updates.</p> <p><strong>Users</strong><br /> This field could be used for all Agencies.</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20079Issue Return Activity Report Enterprise Rollup00767WarehouseUSMC: CSPDoneSubmitted: 16 Jan 2015<p><strong>Description</strong><br /> During operations within the NCR there are numerous metrics requested out from the CSP PMO that come from the issue/return activity report (how many issues per week, how many returns per week, number of items issued, etc…). To get that data today, the NCR area manager is forced to log in to each of her warehouses to create a consolidated report. Because we have to go through each WH, and pull the data separately creates the possibility for errors in the report.</p> <p><strong>Recommended</strong><br /> It is requested that the DPAS-WM be updated to include enterprise roll-up capability for the issue return activity in the DPAS-WM.</p> <p><strong>Mission Critical</strong><br /> Due to the high frequency requirement for the NCR Area manager to provide details about her operations, this requirement is mission critical for implementation at Beaufort, SC and rollout to Camp Lejeuene.</p> <p><strong>Benefits</strong></p> <p><strong>Users</strong></p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20078Adding Services Performed to the main GRID00803WarehouseUSMCDoneSubmitted: 03/26/2015<p><strong>Description</strong><br /> In Materiel Management, Quality Control, customer need the capability to view and search Service Performed actions.</p> <p><strong>Recommended</strong><br /> Recommend adding Service Performed to the main GRID line in Quality Control.</p> <p><strong>Mission Critical</strong><br /> Yes, because customer needs visibility of work performed by M&U personnel.</p> <p><strong>Benefits</strong><br /> The benefit is this process will reduce errors make it possible for QC to track maintenance performed by M&U personnel.</p> <p><strong>Users</strong><br /> All</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20077Default Return to Individual Issue location00798WarehouseUSMCDoneSubmitted: 12 Jan 2015<p><strong>Description</strong><br /> 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.</p> <p><strong>Recommended</strong><br /> Have ability to update Individual Issue Locations to be set up as a default return locations.</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong><br /> 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.</p> <p><strong>Users</strong><br /> This would impact all users if they chose to make default locations.</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20076Exchange equipment00769WarehouseUSMC: CSPDoneSubmitted: 16 Jan 2015<p><strong>Description</strong><br /> While implementing the DPAS-WM at the NCR we observed on many occasions where a member decided that the sizing on the item they were issued was wrong and they returned to the WH to exchange the item that they were issued. Within the DPAS-WM as it is currently designed, an exchange is a very time consuming process that involves going through the member entire list, returning the item being exchanged and then a subsequent issue of the new size. There is simply too much time and labor involved in the process.</p> <p><strong>Recommended</strong><br /> We need the capability to exchange equipment in the system. Our vision behind this is that we will see the following options under the Individual and Unit menus of Material Management:</p> <p>Individual:</p> <ul> <li>Issue</li> <li>Exchange</li> <li>Temp Loan</li> <li>Return</li> </ul> <p>Unit:</p> <ul> <li>Issue</li> <li>Approve</li> <li>Exchange</li> <li>Return</li> </ul> <p>It should be set so that there is an exchange tab on the individual issue options. When exchange is selected, the member’s current issued equipment should display on the screen. The clerk must then be able to select the item(s) being exchanged, and then swap either change the size or NSN of the item the exchange is being requested for. When an item is exchanged, the system should pull the exchanged item from the individual issue location, and return the returned item to the appropriate return location. For items that are exchanged for the same like item (due to damage or something along those lines, the clerk must be able to input the reason for the exchange.</p> <p><strong>Mission Critical</strong><br /> This is a Mission Critical Requirement due to the time consuming nature of the exchange process as it is currently designed. Not having the ability to rapidly exchange equipment impacts around 10% of the business at the NCR.</p> <p><strong>Benefits</strong><br /> The benefit of updating this process will be a method for the DPAS-WM to record exchanged equipment and time savings at the counter.</p> <p><strong>Users</strong><br /> This will impact all DPAS-WM Unit and Individual Issue Process users.</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20075Process for quicker Serial-Unmanaged kit Returns00754WarehouseUSMC: CSPDoneSubmitted: 16 Jan 15<p><strong>Description</strong><br /> The return of serialized kits in the DPAS-WM is a painful process, often taking over 5-10 seconds per item that needs to be verified. This process needs to be updated to provide a verify all capability. Within the DPAS-WM, when a serialized item is being returned, the system does not have the capability to "verify all" parts coming across the counter. The important thing to remember here is that the verification of parts is simply in the system to work if exception exist and should not serve as the real check. The check is a site verification from experienced clerks. Given that, the clerks need a quick way to verify all parts during a receipt. Without the verify all capability we are often finding the clerks spending 5 seconds per item on the list to complete asset verification. For a Gas Mask, that is over 3 minutes verifying parts for one serialized item, not to mention is there are others. The main thing that is needed here is velocity. Transactions should be able to be processed quickly, rather than the tedious process that serialized parts verification is.</p> <p><strong>Recommended</strong><br /> It is requested that the verify all capability that is in place for bulk kits be made available to serialized items within the system as well. The verification is happening at the time of receipts via sight verification and action at the counter, and we do not need a tedious process to go through.</p> <p><strong>Mission Critical</strong><br /> This is a mission critical requirement because the return of serialized kits is unsustainable as it is currently designed. The example we have been seeing at the NCR are those Marines who have NBC gear. For those Marines, the verification of equipment is taking significantly longer than bulk only returns. The process is quite painful, and is even nastier on the Unit Issue side of the house.</p> <p><strong>Benefits</strong><br /> The benefit of developing this capability will be a time reduction in processing serialized kit returns.</p> <p><strong>Users</strong><br /> This impact will benefit all DPAS_WM users who issue//return serialized kits.</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20074COSIS QC Request00701WarehouseUSMCDoneSubmitted: 11/18/2014<p><strong>Description</strong><br /> System generated COSIS Quality Control Requests contain assets on multiple locations. They seem to be sorted by stock number only. This means that on a single QC Request, there could be a massive amount of assets of different condition codes and different locations. This will create a lot of lost time for the assigned inspector to find all of the assets on that request on multiple locations and multiple condition codes.</p> <p><strong>Recommended</strong><br /> System generated COSIS QC Request should be generated separately by like stock number and then by like location. Stock numbers with more than one location should be scheduled as different COSIS request. Mixed condition codes can be requested on the same request as long as the locations and stock numbers are the same.</p> <p><strong>Mission Critical</strong><br /> This is mission critical, this would prevent unnecessary man hours to be used traveling to multiple locations.</p> <p><strong>Benefits</strong><br /> The benefit is if these requests were scheduled by lot (location), this would reduce the man hours required to work each request. Therefore reducing costs and increasing productivity.</p> <p><strong>Users</strong><br /> All</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20073Mass Edits of Missing Gear00675WarehouseUSMC: CSPDoneSubmitted: 7 July 2014<p><strong>Description</strong><br /> Non-standard returns, missing gear statements, custom (non-unit issue list) transactions are one at a time and are time consuming. This process needs to be improved. This is critical prior to DPAS implementation at Camp Lejeune and beyond. This comes down to clickology in the system. It is overly burdensome to process a large individual issue return, when there are many missing items, and other issues to deal with.</p> <p><strong>Recommended</strong><br /> It is requested that DPAS/LEIDOS provide the capability to process missing gear statements for all items listed on the missing gear statement in Mass, thereby reducing the number of key strokes involved in completing the process.</p> <p><strong>Mission Critical</strong><br /> Yes, this will significantly impact on our customer processing time. We cannot implement at Camp Lejuene and beyond without a smoother process in place.</p> <p><strong>Benefits</strong><br /> Implementing this design request will reduce users time for processing transactions and members wait time to receive their receipts.</p> <p><strong>Users</strong><br /> Yes, this will impact all of CSP DPAS users.</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20072Spreadsheet Upload Process for OCS, TBS, SOI, East and West00674WarehouseUSMC: CSPDoneSubmitted: 06 August 2014<p><strong>Description</strong><br /> OCS,TBS, SOI East/West classes provide rosters in advance to the IIF. All of OCS and 80 % of TBS students do not have CAC cards issued to them. At this time DPAS doesn't provide a way to upload these lists in a batch upload process. Each name has to be key punched one at a time.</p> <p><strong>Recommended</strong><br /> Adding a Batch upload process for OCS,TBS,SOI East/West class rosters.</p> <p><strong>Mission Critical</strong><br /> Yes, this is mission critical. With limited staff at OCS,TBS,SOI East/West IIF's it is critical to have a Batch upload process to save time.</p> <p><strong>Benefits</strong><br /> Reduces Time/Cost.</p> <p><strong>Users</strong><br /> Yes, this will impact 80% of CSP DPAS users.</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20071WM Enterprise User00792WarehouseDFAS ColumbusDoneSubmitted: 2/13/15<p><strong>Description</strong><br /> 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.</p> <p><strong>Recommended</strong><br /> 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:</p> <ul> <li>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.</li> <li>Security – This is already in use. The only role that can be assigned is Security. No change is being requested.</li> <li>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.</li> <li>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.</li> <li>Admin Console – The only available role for this user should be Job Schedule Manager.</li> </ul> <p><strong>Mission Critical</strong><br /> 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. <br /> 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:</p> <ul> <li>User Type Codes within the application create a clear separation of duties. <br />Users’ can only be assigned one User Type Code. <br />They are as follows: <ul> <li>Standard User – Used for the majority of users</li> <li>Security Officer – Only used for DPAS User Account Management in Columbus, OH</li> <li>Application Administrator – Assigned to the DPAS Support Desk. Inquiry only access to assist callers requiring assistance.</li> <li>DPAS Agency Coordinator – Typically one or two users per agency. User has the ability to determine a few agency setting and inventory plans.</li> <li>DPAS Administration Console – Used to monitor the general health of the system. Only assigned to DPAS Columbus and Leidos staff.</li> </ul> </li> </ul> <p><strong>Benefits</strong><br /> 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.</p> <p><strong>Users</strong><br /> This SCR is needed to be in compliance of the upcoming SSAE 16 audit.</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20070Gain Serialized Item00678WarehouseUSMC: DMCDoneSubmitted: 23 July 2014<p><strong>Description</strong><br /> During ADHOC testing of the DPAS-WM we attempted to perform an inventory gain as if for the purposes of having found an item during a directed inventory. The DPAS WM will not allow for the user to add material to the system other than through the receipts process. There are cases where it is DOD order to add material for other than receipted for reasons.</p> <p><strong>Recommended</strong><br /> The system must have the functionality to add material via the Inventory manager update process for gains associated with physical inventories. The lack of functionality on this end forces the user to ad the material via receipt only, which puts out a different SCS transaction than what is required.</p> <p><strong>Mission Critical</strong><br /> Yes, without this functionality DPAS-WM users will have to perform receipt transactions for gains associated with a physical inventory. While there is functionality to get the material in the system, this violates USMC policy on physical inventory.</p> <p><strong>Benefits</strong><br /> This update makes the DPAS-WM conform to USMC policy and allignes with SCS Financial Reporting requirements for gained and lost equipment.</p> <p><strong>Users</strong><br /> Adding this functionality will benefit the entire DPAS community.</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20069Display Product Code on Intermec CN3 Handheld00742WarehouseUSMC: DMCDoneSubmitted: 1/05/2015<p><strong>Description</strong><br /> No project code displays on the Intermec CN3 handheld during the receipt process.</p> <p><strong>Recommended</strong><br /> Project code must be displayed so assets can be identified at the time of receipt. Assets of the same stock number will be ordered on many different project codes and can't be identified without this information.</p> <p><strong>Mission Critical</strong><br /> Yes, Project codes can not be identified without the project listed on the grid.</p> <p><strong>Benefits</strong><br /> The benefit is this will be automated rather than writing it on each document.</p> <p><strong>Users</strong><br /> All</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20068Container WH Transfer00738WarehouseUSMC: CSPDoneSubmitted: 16 Dec 2014<p><strong>Description</strong><br /> The CSP Program frequently moves batches of 1500 serialized SAPI Plates between the NCR IIF and the Camp Lejuene X-Ray Facility. In addition, those SAPI plates are shipped back from Camp Lejuene to the NCR DC, and the DC will replenish the IIF as required. The problem we are having is in the time consuming nature of processing these shipments. in DPAS it takes between 2 and 5 seconds per serial number to process a shipment of serialized items. Given the 5 second worst case scenario, it will take NCR personnel over 2 hours of uninterrupted system time to complete a transfer or MRO of these items. In their previous system, LVI personnel could ship a container containing 1500 serial number in 2 minutes or less.</p> <p><strong>Recommended</strong><br /> It is requested that the DPAS-WM be updated to allow for the system to process containerized shipments of material for warehouse transfers, dispositions, and MRO's being shipped from the a warehouse to make serialized items easier to ship. If a container is chosen to ship, the system should automatically select all serialized and other material in the container and manifest that info on the 1348 for shipment to another facility or program (External system).</p> <p><strong>Mission Critical</strong><br /> This is a critical system change requirement, becuase the orginizational structure of the CSP Program is not currently staffed to dedicate the time needed to ship serialized items from the warehouse the way the system is currently designed. In addition, it is difficult for any user to commit the amount of uninterrupted system time needed to complete a serialized transfer, disposition, or MRO.</p> <p><strong>Benefits</strong><br /> The proposed fix will serve to make processing time of MRO's, dispositions, and transfers of serialized 60 times faster, and will be more in line with aid NCR in meeting its personnel staffing needs without having to hire more personnel to handle the arduous job of entering 1500+ serial numbers for shipment as the system is currently designed.</p> <p><strong>Users</strong><br /> Yes, this will impact all of CSP, DMC, and other system users across the enterprise.</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20067Manual Signature Pad00764WarehouseUSMC: CSPDoneSubmitted: 16 Jan 15<p><strong>Description</strong><br /> When the manual sign is selected, it is requested that the system work with a signature pad to capture an image of the signature and record that signature on the issue receipt vice printing a unsigned form. The current signature pad used by LVI is the Topaz Systems Inc 1x5 pad Model Number T-S261-PLB-R. Exacerbated by the fact that many CSP Customers do not have access to the system. At the CSP NCR Pilot Implementation site it has been discovered that e-sign capability in the system is both inconsistent, and that USMC members do not always know their CAC PIN. Many of NCR Customers are new to the Marine Corps and have yet to establish and use DOD E-Mail accounts, let alone DOD computers. As a result, many students do not know their PIN's and Cannot e-sign.</p> <p><strong>Recommended</strong><br /> It is requested that the DPAS-WM be update to use an electronic signature pad for all manual sign transactions completed in DPAS. The signature pad used by LVI today is the Topaz Systems Inc 1x5 pad Model Number T-S261-PLB-R. Once a signature is captured in this manner it should electronically display on the members issue/return/temp loan/exchange/CMR Reconciliation forms for future audits.</p> <p><strong>Mission Critical</strong><br /> This is mission critical for a few reasons:</p> <ol> <li>Due to e-sign and user issues with their PIN numbers, we need the ability to capture proof that a member signed for his gear in the system. This can be audited for future reconciliations as needed.</li> <li>This capability is needed to reduce the time it takes to print, sign, and upload receipts to the system.</li> </ol> <p><strong>Benefits</strong><br /> The benefits of implementing the electronic signature pad are that, if e-sign capability is down, users can still sign with an auditable signature that will show up in the system. In addition, this will save us time and aid in record accuracy long term.</p> <p><strong>Users</strong><br /> This impacts all DPAS-WM users.</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20066Freeze Headers on All Screens00672WarehouseUSMC: CSPDoneSubmitted: 06 Aug 2014<p><strong>Description</strong><br /> In the columns that are displayed in each DPAS menu screen, need to have column headers and left to right scroll bar freeze on screen when scrolling up and down.</p> <p><strong>Recommended</strong><br /> Freeze column Headers and all screens.</p> <p><strong>Mission Critical</strong><br /> Not mission Critical but would greatly enhance ability for the USER to know which column is which when looking at screens with more than 10 rows of data.</p> <p><strong>Benefits</strong><br /> Improves Accuracy when looking at screens with more than 10 rows of data.</p> <p><strong>Users</strong><br /> Yes, this will impact all of CSP DPAS users.</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20065Allow training date updates for multiple users00411PADFAS ColumbusDoneSubmitted: 10 June 2009<p><strong>Description</strong><br /> Allow the Training Coordinator the ability to apply training dates to multiple roles for a user at one time. The process takes about 2 minutes for each role for a user.</p> <p><strong>Recommended</strong><br /> Allow the Training Coordinator the ability to apply training dates to multiple roles for a user at one time. The process takes about 2 minutes for each role for a user. By allowing the Training Coordinator to apply training dates to multiple roles for a user at one time it will greatly speed up the current process.</p> <p><strong>Mission Critical</strong><br /> No</p> <p><strong>Benefits</strong><br /> The training coordinator is tasked with preparing User Ids for on-site training and preparation for major testing events such as SIT or SAT. Adding a class of twenty takes over 2 hrs. – depending upon the lag between the multiple screen refreshes, when it should be able to be completed in 20 - 25 minutes.</p> <p><strong>Users</strong><br /> This will affect all Training Coordinators and the DPAS Support Office.</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20064Add DD Fm 1149 and DD Fm 1149C00292PAHQ-DODEADoneSubmitted: 12/31/2001<p><strong>Description</strong><br /> DD Form 1149 And 1149c, Requisition And Invoice/Shipping Document And Continuation Sheet, Are Standard DoD Shipping And Receiving Documents. In The Pacific Command The Air Force Transporters Require The DD 1149 As The Shipping And Receiving Document For All Government Property. DPAS Users In The Pacific Area That Must Use The Air Force Transportation System Must Use An Off-Line Forms Writing Program To Generate The Dd1149 Forms. Also Stateside DODEA Activities Use The DD1149 For Lateral Transfer Of Government Property.</p> <p><strong>Recommended</strong><br /> DPAS Generate The Dd1149 Forms. The Required Equipment Data That Must Transfer From System To The DD1149 Are DoDAAC Of Losing And Gaining Activity, Stock Number, Noun, Bar Code, And Serial Number.</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong></p> <ol> <li>Eliminates The Need To Use Another Source To Generate Form.</li> <li>Eliminates The Possibility Of Mistakes When Info, Such As Barcode, Stock Number, Etc., Is Typed To An Off-Line Form.</li> <li>Brings DPAS In Line With DoD Logistics Standards</li> </ol> <p><strong>Users</strong></p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20063Forms-Reports Pending Trans Report Query UIC00445PADPAS - CDoneSubmitted: 12/17/2009<p><strong>Description</strong><br /> Under Forms – Reports > View Forms / Rpts for the Pending Transaction Report add the capability to query on a single UIC or All UICs</p> <p><strong>Recommended</strong><br /> The capability is needed to narrow down the report to a specific UIC for quicker assessment of pending actions resulting in a quicker turn-around time on processing.</p> <p><strong>Mission Critical</strong><br /> Current report can contain hundreds of assets “Pending In Actions” or “Pending Out Actions” for 80+ UICs. It is time consuming for the Property Book Officer for a specific UIC to have to look through many pages of pending actions that do not belong to their UIC.</p> <p><strong>Benefits</strong><br /> A quicker turn-around time on processing pending transactions.</p> <p><strong>Users</strong><br /> Affects all Users in Agency.</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20062Mass loan of Government owned Property outside DPAS00650PADMADoneSubmitted: 12 October 2010<p><strong>Description</strong><br /> Allow for mass transfer of government owned property instead of an item by item (based on asset ID). Currently the process entails each item be individually moved, this is a time consuming task that should be available as a single transaction.</p> <p><strong>Recommended</strong><br /> Create a means whereby the transfer of multiple items (if placed in a dedicated location or hand receipt, or via a stock number search can be mass transferred to a contractor as GFP.</p> <p><strong>Mission Critical</strong><br /> As Agencies are turning over control of GFP to contractors it is imperative that the action be done in the most expeditious manner.</p> <p><strong>Benefits</strong><br /> This process reduces time/cost since it would require less of each on the past of the Accounting Officer. This process would also improve accuracy/accountability since all of the property is being accessed onto the database at the time of acquisition and would reduce errors in the process.</p> <p><strong>Users</strong><br /> Transfer of GFP should affect users across all DPAS customers</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20061Add Attachment to Asset Outside of Asset Update00661PANavyDoneSubmitted: 4 Feb 2014<p><strong>Description</strong><br /> Need functionality to add attachments to asset records during the receiving and during location change process. Current process only permits attachments during the asset update process. Examples of the issue:</p> <ul> <li>when updating several similar barcodes to a new location, it would be nice to be able to attach the DD Form 1149 (source document) to all of the records at once, instead of having to perform multiple transactions to add the attachment.</li> <li>When adding the assets to DPAS, the first several screens consist of load data that is the same for the whole asset group. The only screen that changes is the last screen, where serial #, barcode #, custodian and location are input. Nowhere in this process, is the property manager afforded an opportunity to attach the contract or any other source documentation, which would support the addition of the assets into DPAS. The only way to add a source document to newly added records is to Update each record individually after the asset is added to DPAS.</li> </ul> <p><strong>Recommended</strong><br /> Allow for attachments to be added to more than one record at a time would save valuable time and therefore free up man-hours to perform other property management functions</p> <p><strong>Mission Critical</strong><br /> Neither. It is a labor saving recommendation.</p> <p><strong>Benefits</strong><br /> Improves audit readiness by permitting the property manager to add audit required documentation to the asset record in a timely manner.</p> <p><strong>Users</strong><br /> yes. it impacts all Agencies using DPAS.</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20060DD Form 1348 does not display the RIC To/From when performing an Asset Disposition00426PAOtherDoneSubmitted: 11/2/2009<p><strong>Description</strong><br /> DD Form 1348 does not display the RIC To/From when performing an Asset Disposition.</p> <p><strong>Recommended</strong><br /> Site does not use the DAISY interface when disposing property. However, site needs to have the RIC To (pos. 67-69) and the RIC From (pos. 4-6) displayed on the DD Form 1348.</p> <p><strong>Mission Critical</strong><br /> the site has to manually enter these fields on every 1348 that is generated</p> <p><strong>Benefits</strong><br /> reduces time and cost and improve accuracy</p> <p><strong>Users</strong><br /> performed by the PBO and other users daily</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20059Add a single attachment to all chosen assets00586PAMDADoneSubmitted: 13 March 2013<p><strong>Description</strong><br /> Currently there is no method to attach a single attachment to multiple assets. It would make DPAS more user friendly to be able to choose multiple items by checking off of a list (much like current transfers) and adding a single attachment to all chosen assets.</p> <p><strong>Recommended</strong><br /> Create a method or the ability to select multiple assets from a UIC through Asset Management>Update process and adding a single attachment to all chosen items.</p> <p><strong>Mission Critical</strong><br /> This would provide a method as required by OSD AT&L to place essential receiving documents to multiple assets in DPAS.</p> <p><strong>Benefits</strong><br /> As contracts are Modified, DPAS users will be able to add a single attachment (copy of the MOD, Spreadsheet and or receiving documents) to multiple assets rather than a single asset at a time.</p> <p><strong>Users</strong><br /> This will affect all users of the system who decide to use this option when multiple assets can be tied to a single document.</p> <p>Also completed SCR <a href="index.php/support/system-change-request/details/4/13594/add-multiple-attachments-to-multiple-assets-at-a-single-time" rel="alternate">00741</a>.</p> <p><strong>Completed - Release 3.0 - 15 May 2015</strong></p>
20058Easily Distinguish QC - Required Items01063WarehouseAF: AFERMSDoneSubmitted: 11/22/2016<p><strong>Description</strong><br /> Units can't easily distinguish which items need QC.</p> <p><strong>Recommended</strong><br /> Adding this check box will make it more user friendly and enable faster more streamlined searches, especially for QCIs and Supervision.</p> <p><strong>Mission Critical</strong></p> <p><strong>Benefits</strong></p> <p><strong>Users</strong></p> <p><strong>Completed - Release 5.1 - 28 April 2017</strong></p>
20057Agency predefined report titled Navy Capitalization Code N or S Errors00662PANavyRemovedSubmitted: 3/18/2014<p><strong>Description</strong><br /> The Agency Pre-Definded report titled Navy Capitalization 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.</p> <p><strong>Recommended</strong><br /> Add the following fields to the Agency Predefined Report - Navy Capitalization Code N or S Error report: Activation Dt, Acq Dt, and Local Rcpt Dt</p> <p><strong>Mission Critical</strong><br /> 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.</p> <p><strong>Benefits:</strong><br /> Will permit Navy to correctly depreciate capital equipment in support of FIAR efforts.</p> <p><strong>Users</strong><br /> All Navy Users</p> <p><strong>16Mar2015 – cancelled per Joe Stossel </strong> <br /> Duplicate of SCR <a href="index.php/support/system-change-request/details/4/14417/agency-predefined-report-capital-code-n-or-s-agency" rel="alternate">00609</a>.</p>
20056Dual Labor Rates00687MUOSDDoneSubmitted: 9/3/2014<p><strong>Description</strong><br /> Reserve and Guard technicians that are also Civilian employees will have dual labor rates. Instead of loading name twice with a different Opr/Tech ID, why not assign both rates under one name?</p> <p><strong>Recommended</strong><br /> M&U Operator/Technician A/U/D should have a field for Labor Rate (Civilian) and Labor Rate (Military) to capture dual rates. When assigning a Technician to a Sub Work, Labor Rate field should be a drop down to chose Civ or Mil rates to charge.</p> <p><strong>Mission Critical</strong><br /> Critical for personnel with dual labor rates to ensure accuracy of rate to charge regardless of employment status.</p> <p><strong>Benefits</strong><br /> Reduces time and improves accuracy of loading technician labor rates to a Maintenance Activity.</p> <p><strong>Users</strong><br /> Maintenance and Dispatch Officer.</p> <p><strong>Completed - Release 3.2 - 06 January 2016</strong></p>
20055Disposition Updates01228EnterpriseArmy: USACENewSubmitted: 6 Nov 17<p><strong>Description</strong><br /> We use the Defense Logistics Agency (DLA) Electronic Turn In Document (ETID's) program for processing excess, in conjunction with DPAS Disposition module for accountability/budget. Each program has a separate document register which are not compatible. This dual document number assignment affects hundreds of excess documents each month.   </p> <p><strong>Recommended</strong><br /> Request the ability to enter a manual document number in the Disposition process.  If this data field is left blank, then it auto-populates in exactly the same manner as DPAS Unit Issue, MILSTRIP, Transfer from External etc... This would give us the flexibility to process both internal and external items identified as excess.</p> <p><strong>Mission Critical</strong><br /> No, but it would allow us to track excess property from when it's first initiated at the customer level, through our excess processing center, to final disposal at DRMO with positive 100% tracking.  In other words, we would obtain excess cradle to grave accountability using one document number generated at the beginning of the turn in process.</p> <p><strong>Benefits</strong><br /> This change would eliminate the need to cross reference the two systems document registers, saving time and confusion when corresponding with an incoming customer and/or DRMO process request.</p> <p><strong>Users</strong><br /> At this time we are the only USACE warehouse using DPAS, so yes it affects all.</p>
20054additional info update01227WarehouseAF: AFERMSDoneSubmitted: 1 NOV 2017<p><strong>Description</strong><br /> currently when we inspect an item we can update kits with the "manage SKO" button, but we still have to go to inventory update manager afterward to update the additional info</p> <p><strong>Recommended</strong><br /> add feature to update additional info when you are updating kit data in the "manage SKO" grid, add a button that is edit additional info</p> <p><strong>Mission Critical</strong><br /> this is a major time savings</p> <p><strong>Benefits</strong><br /> time savings for user</p> <p><strong>Users</strong><br /> all AFERMS users</p> <p><strong>Completed – Release 6.2 – 31 August 2018</strong></p>
20053customer sizes inquiry01226WarehouseAF: AFERMSDoneSubmitted: 1 NOV 2017<p><strong>Description</strong><br /> In order to find my sizes for a member I have to search for the member, click edit, and view the size categories tab.  There is no export feature.  To find my authorized sizes for a unit, I have to do this for each member and hand jam the data into an excel doc.</p> <p><strong>Recommended</strong><br /> add inquiry "member sizes". <br /> make a search by warehouse (search all UICs assigned to a warehouse), UIC, or member. <br /> Allow roll-up to LP, region, site. <br /> display a grid with members as rows and size categories as columns.</p> <p><strong>Mission Critical</strong><br /> critical: I have data in the system that I cannot export. Information is already in an SKO per member anyway.</p> <p><strong>Benefits</strong><br /> huge time savings, elimination of error form hand transferring data</p> <p><strong>Users</strong><br /> all AFERMS users</p> <p><strong>Completed – Release 6.0 – 27 April 2018</strong></p>
20052Update DPAS Real Property Processes to comply with RIPM 10.001225PADPAS: CNewSubmitted: 10-30-2017<p><strong>Description</strong><br /> RPIM 10.0 has been released.  DPAS needs to update its Real Property processes to the new RPIM Model</p> <p><strong>Recommended</strong><br /> Review and compare RPIM 10.0 to DPAS making the noted changes.</p> <p><strong>Mission Critical</strong><br /> Yes.  With DPAS being a Real Property Management System, it needs to stay in compliance with the DoD RPIM model.</p> <p><strong>Benefits</strong><br /> DPAS will be able to comply with RPIM and be compatible with the data.</p> <p><strong>Users</strong><br /> Only Defense Agencies that use DPAS to manage their Real Property</p>
20051Army Data exports01224PAArmy: USASOCNewSubmitted: 10-30-2017<p><strong>Description</strong><br /> DPAS does not produce files that can be uploaded to external systems for the Army.</p> <p><strong>Recommended</strong><br /> Require output data files to integrate with external property accountability applications (JLDW/IMS/ATLAS/SMARTRACK/GFEBS-SA/TDA Reconciliation Application/Excess Management Application). <br /> Army owes the file layouts.</p> <p><strong>Mission Critical</strong><br /> Mandated for asset visibility.</p> <p><strong>Benefits</strong><br /> Automates reporting to systems external to the property book.</p> <p><strong>Users</strong><br /> All Army users.</p>
20050Use of DA Forms01223PAArmy: USASOCIn ProgressSubmitted: 10-30-2017<p><strong>Description</strong><br /> DPAS does not produce all of the required DA Forms</p> <p><strong>Recommended</strong><br /> Require DA Forms for use in DPAS.</p> <ul> <li>DA Form 2062 "Hand Receipt/Annex Number" - used for hand receipt, component annex, temporary hand receipt, inventory list. </li> <li>DA Form 2765-1 "Request for Issue or Turn-in" - used for FOI transactions. </li> <li>DA Form 3161 "Request for Issue  or Turn-in" - used for lateral transfers, change document, temporary hand receipts (loan). </li> <li>DA Form 3161-1 "Request for Issue  or Turn-in (Continuation)". </li> <li>DA Form 4949 "Administrative Adjustment Report"  - used for serial/lot number changes, change in accountability, consumption, assembly, disassembly, catalog changes. </li> <li>DA Form 581 "Request for Issue or Turn-in of Ammunition" - used for requesting or turning in of ammunition.</li> </ul> <p><strong>Mission Critical</strong><br /> Mandated:</p> <ul> <li>DA Form 2062 - AR 710-2, para 2-10g,</li> <li>DA Form 2765-1 - AR 710-2, para 2-8h,</li> <li>DA Form 3161 - AR 710-2, para 2-13a,</li> <li>DA Form 4949 - AR 710-2, para 2-5o,</li> <li>DA Form 581 - AR 710-2, para 2-6, para 2-20d(1)</li> </ul> <p><strong>Benefits</strong><br /> Provides forms required by Army.</p> <p><strong>Users</strong><br /> All Army users.</p> <p><strong>Partially Completed – Release 2020.2 – 26 June 2020</strong></p>
20049Email Notification of FEDLOG updates01222PAArmy: USASOCNewSubmitted: 10-30-2017<p><strong>Description</strong><br /> DPAS does not send notifications to the PBO for catalog changes made at the FEDLOG level. </p> <p><strong>Recommended</strong><br /> Send PBO emails of changes that were made to assets on Property Book due to FEDLOG updates.</p> <p><strong>Mission Critical</strong><br /> Mandated by AR 710-2, para 2-5o / AIS Manual PBUSE EUM</p> <p><strong>Benefits</strong><br /> Provides automated notification to PBO.</p> <p><strong>Users</strong><br /> All Army users</p>
20048Army Hand Receipt01221PAArmy: USASOCDoneSubmitted: 10-30-2017<p><strong>Description</strong><br /> DPAS hand receipt does not contain data elements required by Army, such as authorization LIN, and quantities</p> <p><strong>Recommended</strong><br /> Require hand receipt generation to include essential data elements required by AR 710-2. <br /> Hand receipt should sorted by Authorization Property Type Code - LIN-NSN/MCN. <br /> Essential Data Elements per AR 710-2, para 2-10g are: </p> <ul> <li>"Hand receipt"</li> <li>"From"</li> <li>"To"</li> <li>"Hand receipt number"</li> <li>"LIN"</li> <li>"NSN/PN/MCN/"</li> <li>"Serial number/registration number/lot number"</li> <li>"Item description"</li> <li>"Hand receipt annex/component hand receipt number (if applicable)"</li> <li>"Controlled inventory item code (CIIC)"</li> <li>"Unit of issue"</li> <li>"Quantity authorized"</li> <li>"Signature, date, and grade/rank"</li> <li>"Quantity on hand"</li> </ul> <p><strong>Mission Critical</strong><br /> Mandated by Hand Receipt accountability required by AR 710-2, para 2-10g. <br /> Direct Responsibility for property required by AR 735-5, para 2-8a(3).  <br /> Change document posting is required by AR 710-2, para 2-10c(5).</p> <p><strong>Benefits</strong><br /> Provides data elements required by Army.</p> <p><strong>Users</strong><br /> All Army users.</p> <p><strong>Completed – Release 7.1 – 26 July 2019</strong></p>
20047Edit Capability for all Catalog Records01220PAArmy: USASOCNewSubmitted: 10-30-2017<p><strong>Description</strong><br /> DPAS does not currently permit editing of FLIS/FEDLOG catalog records.</p> <p><strong>Recommended</strong><br /> Require ability to maintain local catalog input and ability to change data elements for FEDLOG and AESIP catalog records. <br /> USASOC should be permitted to edit any catalog records or create records that are not on the Master catalogs.</p> <p><strong>Mission Critical</strong><br /> Mandated by AR 710-2, para 2-10i(1)</p> <p><strong>Benefits</strong><br /> Permits USASOC to control their catalog.</p> <p><strong>Users</strong><br /> All Army users.</p>
20046SKO Management01219PAArmy: USASOCNewSubmitted: 10-30-2017<p><strong>Description</strong><br /> End Item and Component capabilities currently in DPAS are not robust or efficient to meet Army requirements.</p> <p><strong>Recommended</strong><br /> Require component management capability in PA module. <br /> Require LOGSA published SKO listings in DPAS PA module for P2 Army common equipment.</p> <p><strong>Mission Critical</strong><br /> Mandated by AR 710-2, para 2-10i(1)</p> <p><strong>Benefits</strong><br /> Provides SKO process required by Army.</p> <p><strong>Users</strong><br /> All Army users.</p>
20045Add DLA Local Stock number to DD1348-1A01218PANavyNewSubmitted: 24 October 2017<p><strong>Description</strong><br /> When processing a Disposition / Disposal transaction (action code = DSPL and an address type - DE) a DD form 1348 DRMO Turn in document is generated from DPAS with the FSC  and nomenclature appearing in the stock number field when the stock number is an MCN.  <br />DLA Disposition Services will not accept the DPAS generated DD 1348 as it does not contain the DLA local stock number (LSN) which is selected from a DLA LSN Master List that is FSC driven.   <br />The DLA LSN is comprised of the FSC and a "material number".   <br />Proposed Solution: Provide a process to permit the stock number field on the DD 1348 to be populated with the DLA LSN when the asset uses a DPAS MCN stock number. </p> <p><strong>Recommended</strong><br /> Several possible solutions exist: </p> <ol> <li>Create a drop down to select a DLA LSN supported by the DPAS asset FSC and nomenclature and add the DPAS MCN stock number to block 27 - additional data for historical cross reference purposes. </li> <li>Permit the DPAS user to manually enter the DLA LSN in the DD 1348 stock number field and the DPAS stock number to block 27 additional data prior to printing. </li> <li>Create a DLA Disposition Services interface with DPAS.   </li> </ol> <p>A copy of the DLA Disposition Services LSN Master list accompanies this SCR. </p> <p><strong>Mission Critical</strong><br /> Not mission critical. But is necessary to reduce the manpower effort to locally create a DD 1348 turn-in document that DLA will accept. </p> <p><strong>Benefits</strong><br /> Reduces the time to create disposition documents to dispose of assets to Defense Logistics Agency.</p> <p><strong>Users</strong><br /> This will be very effective in processing disposal documents for all DOD components/Agencies.  </p>
20044Add Status to UIC Inquiry01217PANavyNewSubmitted: 24 October 2017<p><strong>Description</strong><br /> In Master Data under Actbl UIC-/UIC is a field called "STATUS".  This field is either Active or Inactive.  Navy has many UIC's (Echelon IV commands) built as custodians under a UIC.   When these custodian UIC's are built in Master data they are built as INACTIVE.  Since there is no filter or field value equal to Status (ACTIVE or INACTIVE) Navy can not run a report to identify INACTIVE UIC address information.  Only Active UIC's are available via the Inquiry / Master Data / UIC module.</p> <p><strong>Recommended</strong><br /> Navy needs the "Status (Active and/or Inactive) field added as a filter to the Inquires/Master Data/UIC process and also add STATUS (Active / inactive) as a "field" selection so that it can be added to an exported file.</p> <p><strong>Mission Critical</strong><br /> Not mission critical.  But needed to support business practices related to UIC management.</p> <p><strong>Benefits</strong><br /> Provides capability to identify address information of a inactive UIC.</p> <p><strong>Users</strong><br /> I should think this would be of interest to other DoD components/Agencies.</p>
20043XML upload to GCSS-A01216PAArmyNewSubmitted: 16 October 2017<p><strong>Description</strong><br /> Approved Program Executive Offices (PEO) need an interim solution to field assets to GCSS-Army units while the Warehouse Module is being constructed and DLMS actions are being worked. Bulk fielding's will require GCSS-Army units to accept manual transactions.</p> <p><strong>Recommended</strong><br /> Automate process for XML upload from DPAS to GCSS-Army. Use ".xsd" file attached to execute transaction.</p> <p><strong>Mission Critical</strong><br /> Mission Critical - need automated process in order field material from DPAS to GCSS-Army while CR3607 is being worked.</p> <p><strong>Benefits</strong><br /> This automated process will reduce time/cost and improve accuracy/accountability by enabling PEO(s) to bring assets into an approved APSR and field without manual effort to GCSS-Army units.</p> <p><strong>Users</strong><br /> YES. It will affect all users who are required to field assets to units via GCSS-Army.</p>
20042IUID Export from HHT01215WarehouseUSMCNewSubmitted: 2 Oct 17<p><strong>Description</strong><br /> Hand held Devices are already capturing whether a serial number was captured from IUID or from being typed into hand held for inventory.   Items not scanned are either missing their IUID tag, or the tag is damaged and not scan-able.  Either way, the IUID tag needs to be remade. </p> <p><strong>Recommended</strong><br /> Export all inventory records that were no scanned from each inventory into an excel spreadsheet.   Option to export un-scanned IUID tagged items should be part of upload process and/or reconciliation process.  Items listed on spreadsheet can have IUID tags remade either locally or remotely.   Each Record should contain NSN or NIN, Serial Number, CAGE code and TAMCN if available.  </p> <p><strong>Mission Critical</strong><br /> MCO 4410.28 mandates use of IUID on all controlled items and items over $5000 in value.  Re-tagging of assets whose IUID tag has either been damaged or lost is therefore necessary. </p> <p><strong>Benefits</strong><br /> Scanning of assets improves both speed and accuracy of counts.  Goal should be to have 100% of all serialized assets with IUID tags and each inventory should reduce the amount of assets requiring new tags.  </p> <p><strong>Users</strong><br /> All services utilize IUID technology so all will be able to utilize this functionality. </p>
20041Utilization/Fuel Variance Report(s)01214MUAF: VSCOSDoneSubmitted: 31 Mar 2017<p><strong>Description</strong><br /> No Fuel Variance Report to identify potential utilization and fuel charges errors.</p> <p><strong>Recommended</strong><br /> DPAS will accept utilization and fuel data but if any transaction is outside of a designated variance (10%+/-) of the last utilization update or last fuel charge; DPAS will capture those assets and send to the Message of Day as an open action report. Example: Message of the Day>Asset>Meter Reading Variance Rpt or/and Utilization Variance Report (they could be one report if it's easier)  Once report appeared in the Maintenance Activity and the report was generated as a Message of the Day Rpt it would be up to the user at the M&U to verify and resolve. Agency policy would address how many days the M&U will have to resolve, i.e. 5 Days</p> <p><strong>Mission Critical</strong><br /> Mandated. It is mandated that AF Maintenance Activities capture and report complete and accurate utilization and fuel charges.</p> <p><strong>Benefits</strong><br /> Provides away for users to not accept potential erroneous data. Gives a visual alert to users to validate data to ensure 100% accuracy.</p> <p><strong>Users</strong><br /> Yes all AF users and other Services and Agencies</p> <p>Combined with SCR #<a href="index.php/support/system-change-request/details/4/20328/dispatch-mileage-flag">00628</a></p> <p><strong>Completed – Release 7.0 – 20 April 2019</strong></p>
20040Asset Warranty Coverage01213MUAF: VSCOSNewSubmitted: 08/10/2017<p><strong>Description</strong><br /> <strong>Problem:</strong> Current DPAS method of tracking warranties at the asset level requires the warranty to be established at the contractor/contract/warranty terms/warranty asset association levels. Current capability is time consuming and requires several steps to identify basic/extended/corrosion/emissions warranties to assets managed in M&U. It also does not allow establishing separate warranty start/end dates at the asset level. i.e., one contract may  procure 10 assets, 5 received in Jan and 5 received in Jun, currently the warranty Clause start date would be Jan for all assets received under this contract. The system needs to identify different warranty start/end dates for contracts supporting assets received over a period of time to capture warranty association at the asset level not the contract level. <br /> <strong>Proposed Improvement:</strong> Vehicles are procured from various manufacturers under contracts which may include different warranty clauses start/end dates which are subject to change based on contract year or date asset was receipted into inventory. Warranty association should be linked at the asset level not the contractor/contract/warranty terms/warranty asset association levels, this will allow users to manage warranty clauses for multiple assets received under the same contract within different time frames throughout the year without having to load numerous contracts to cover warranty asset associations. </p> <p><strong>Recommended</strong><br /> <strong>Solution #1:</strong> Clause Start Date and End Date should be moved to the Asset Association > Create a Add/Delete function. Once the asset reaches its warranty expiration the warranty date would be automatically dropped from the system. Fields to identify the warranty clause/terms can remain the same but at the asset level. This will allow the warranty start/end dates to be assigned at the Asset Level not the contract Level. The AF centrally procures vehicle assets and some of these contracts are active for many years procuring hundreds of assets annually with differing delivery dates. Current DPAS capabilities mandates the same contract # be loaded with differing CLIN or RPN if on GSA schedule to associate each asset warranty start/end date to separate buys under the same contract. <br /> <strong>Solution #2:</strong> Do not link warranty association to any contractor/contract information. Warranty terms are established at the asset record in M&U establishing start date and end dates to track warranty term. Once the asset reaches its warranty expiration the warranty date would be automatically dropped from the system. Fields to identify the warranty clause/terms can remain the same but at the asset level. Both solutions would eliminate the requirement associate the asset warranty to contractor/contract.    </p> <p><strong>Mission Critical</strong><br /> Yes, AFI 24-302, para 4.5. mandates the review of all repairs to determine if covered by a new vehicle warranty or a previous contract, COPARS or other parts warranty. TO 36-1-191 establishes procedures for identifying, reporting, and tracking deficiencies and warranties on AF motor vehicles/equipment. The AF uses the FMIS to manage and track vehicle and part warranties linked to assets.</p> <p><strong>Benefits</strong><br /> Solutions will reduce steps required to load warranty information at the asset level for tracking and display within the MAM. It will also improve the accuracy of inputting and updating warranty terms and conditions based on vehicle receipt date into inventory.</p> <p><strong>Users</strong><br /> This will directly effect ALL users with DPAS who are now mandated to use DPAS as the FMIS to manage all NTV along with the AF who manages all AF owned vehicle assets in DPAS.</p>
20039Lock/Freeze Locations01212WarehouseUSMC: CSPDoneSubmitted: 27 Sept 2017<p><strong>Description</strong><br /> Currently in the DPAS-WM there is a Freeze Location Check Box when you edit or add a location.  Currently checking this box is not doing anything, we are still able to move items in and out of the location.  Recommend that the when the freeze locations check box is checked that no items are allowed to be moved in or out of this location.     </p> <p><strong>Recommended</strong><br /> Recommend that the when the freeze locations check box is checked that no items are allowed to be moved in or out of this location.     </p> <p><strong>Mission Critical</strong><br /> Yes this will help keep accurate inventory during the inventory process and also help us with our Quarantine Items that is mandated by Headquarters Marine Corps and Syscom to be stored in a Locked or frozen location so nothing can be taken out or put into this Quarantine location.</p> <p><strong>Benefits</strong><br /> Having this functionality will help warehouses keep accurate Inventory accountability.  Which will improve the accuracy of reporting from the warehouse level.</p> <p><strong>Users</strong><br /> All IIF/UIF</p> <p><strong>Completed - Release 2021.3 - 10 Sept 2021</strong></p>
20038M&U Operator Profile Load01211MUOSDNewSubmitted: 25 September 2017<p><strong>Description</strong><br /> Currently no way to mass load M&U Operator and Technicians into DPAS.  Currently have to build records one at a time.  Using WH Member Profile conversion process will allow for mass loading during conversion and put all users on one table that can feed any module.</p> <p><strong>Recommended</strong><br /> Data field association between Member Profile and Opr/Tech AUD is very similar and would close SCR 636/<a href="index.php/support/system-change-request/details/4/20290/customer-unit-id">638</a>/665/<a href="index.php/support/system-change-request/details/4/14467/edi-for-oper-tech-id">864</a>: </p> <ul> <li>Logistics Program Name (WH) = Maintenance Activity Name (MU)</li> <li>EDIPI would replace Opr/Tech ID</li> <li>Mbr Category Code Desc would replace Rate Type Assoc</li> <li>Cert/License and Labor Rate assignment can remain in M&U since it is determined by MA but built at a later date</li> </ul> <p><strong>Mission Critical</strong><br /> Critical to the initial loading of personnel who would work on or be dispatched assets out of M&U similar to those issued gear out of WH.</p> <p><strong>Benefits</strong><br /> Reduces time and cost of individual member loading.  Improves data accuracy when all modules use the same member table.</p> <p><strong>Users</strong><br /> All</p>
20037Materiel Movement and QC add to Individual Issue01210WarehouseNavy: NECCNewSubmitted: 7/13/2017<p><strong>Description</strong><br /> NECC would like to use a sized Master Issue List, based on Member Profile for individual issue. Their business process needs to have a way to send the stock number list through the Materiel Movement process for picking and staging. Would also need a QC action as optional at the completion of the pick.</p> <p><strong>Recommended</strong></p> <ol> <li>Create an optional 'Uses Materiel Movement for Individual Issue Processes?' check box, above the 'Uses QC Processes?' in the Update Warehouse screen.  <br />By checking the box, Materiel Movement during Individual Issue is used.<br />  Should also include a 'Send to QC'</li> <li>Add a button to the Individual Issue process bar that enables the pick to go through the Materiel Movement process. </li> <li>(Possibly) Add another button to send the pick to QC once fully picked and staged.</li> </ol> <p><strong>Mission Critical</strong><br /> Mission critical as NECC is unique in that deploying service members do not go to a warehouse to receive their Master Issue List.  The equipment is picked for them and then shipped via UPS.</p> <p><strong>Benefits</strong><br /> As developed now, the individual issue process is coded solely support an Issue Facility were the Member picks their own assets.  By enabling the Material Movement process, warehouse technicians can now use AIT to pick and stage the pick list.  Add QC improves accuracy of the pick before it is signed for.</p> <p><strong>Users</strong><br /> This has the potential to affect ALL Warehouse users.</p>
20036USSGL Updates01209PALeidosNewSubmitted: 9/20/2017<p><strong>Description</strong><br /> The SFIS "Standard Financial Information Structure" has recently published the FY18 list of USSGL "United States Standard General Ledger" account structure for use within DoD.  As a financial feeder system, DPAS does provide its users with a pseudo Trial Balance. While it would not be required to conform the SFIS USSGL chart of accounts, it would be beneficial to its users to make it easier crosswalk the values in DPAS to their actual Trial Balance being produced from the Financial System, should the agency wish to do so. Today, DPAS's USSGL General Ledger Account Code consist of a 4 digit primary USSGL and a 2 digit sub USSGL. The SFIS General Ledger Account Code consists of a 6 digit primary USSGL and a 4 digit sub USSGL. <a href="http://dcmo.defense.gov/Products-and-Services/Standard-Financial-Information-Structure/"><u>http://dcmo.defense.gov/Products-and-Services/Standard-Financial-Information-Structure/</u></a></p> <p><strong>Recommended</strong><br /> Modify the DPAS GLAC Reference Lookup table to support a 6 digit primary USSGL and a 4 digit sub USSGL and implement the values contained within the SFIS USSGL Transaction Library.  DPAS does have several point accounts than what the SFIS USSGL Transaction Library includes as it points the asset accounts to denote Funded and Unfunded amounts as well as for Military Equipment, Non-Military Equipment within GLAC 175000 along with the capability to identify at the Trial Balance level equipment that is In Use, In transit, and Not In Use.  This change would apply to the PA and Materiel Mgt modules of DPAS. </p> <p><strong>Mission Critical</strong><br /> This SCR is considered essential for those users who do not have an automated interface with their financial accounting system.</p> <p><strong>Benefits</strong><br />Update DPAS's USSGL to conform to the SFIS USSGL Transaction Library.</p> <p><strong>Users</strong><br /> This SCR would affect any customer that has a financially reportable asset.</p>
20035Work Order/Sub Work Order01208MUDLANewSubmitted: 9-6-2017<p><strong>Description</strong><br /> Problem: There's a need for an inquiry/report that provides the ability to query both the work order and sub work order together.</p> <p><strong>Recommended</strong><br /> Develop a query that will allow you to query the work order and sub work order together. Inquiries>Work Order>Query Type></p> <p><strong>Mission Critical</strong><br /> This is mission critical because it will assist maintenance managers with workload planning and maintenance shop efficiency, along with maintenance history records for their activity. It will also provide the ability to monitor open work orders and internal performance of equipment currently needing repairs and/or parts. The inquiry needs to include:</p> <ul> <li>Maint Activity,</li> <li>Work Order ID,</li> <li>Asset ID,</li> <li>DoD Serial number,</li> <li>MFR year,</li> <li>MFR name,</li> <li>model,</li> <li>work order state code,</li> <li>status code,</li> <li>equipment pool</li> </ul> <p>at the minimum.</p> <p><strong>Benefits</strong><br /> This will benefit all activities in DPAS by reducing time, while allowing maintenance managers the ability to monitor and effectively manage the use and repair of equipment within their fleet.</p> <p><strong>Users</strong><br /> This should affect ALL users within DLA and DoD utilizing DPAS.</p>
20034Member Size Report01207WarehouseAF: AFERMSDoneSubmitted: 12 Sept 2017<p><strong>Description</strong><br /> Report that includes all the members sizes to include member Attributes and equipment types.</p> <p><strong>Recommended</strong><br /> Build a report that ties to the attributes and equipment types tab of member sizes.</p> <p><strong>Mission Critical</strong><br /> desired</p> <p><strong>Benefits</strong><br /> time savings reduction as the report can be printed and an individual can go into warehouse and pull sizes to fit members.</p> <p><strong>Users</strong><br /> all</p> <p><strong>Completed – Release 6.3 – 21 December 2018</strong></p>
20033PM Report01206MUDLANewSubmitted: 9-6-2017<p><strong>Description</strong><br /> Problem: There's a need to have an inquiry/report that provides the ability to pull a report that will list Equipment Type, PM Type, Task, Parts, Labor Hours, etc per asset and per asset type.</p> <p><strong>Recommended</strong><br /> Develop a query that will allow you to pull a report that will list Equipment Type, PM Type, Task, Parts, Labor Hours, etc per asset and per asset type.</p> <p><strong>Mission Critical</strong><br /> This is mission critical because it will assist managers when contractors have to submit re-competes for contracts. This information is vital because the contractors use this information to determine bidding on contracts for maintenance.</p> <p><strong>Benefits</strong><br /> This will benefit all activities in DPAS by reducing time, while allowing maintenance managers the ability to monitor and effectively manage the use and repair of equipment within their fleet.</p> <p><strong>Users</strong><br /> This should affect ALL users within DLA and DoD utilizing DPAS.</p>
20032PM Report01206MUDLANewSubmitted: 9-6-2017<p><strong>Description</strong><br /> Problem: There's a need to have an inquiry/report that provides the ability to pull a report that will list Equipment Type, PM Type, Task, Parts, Labor Hours, etc per asset and per asset type.</p> <p><strong>Recommended</strong><br /> Develop a query that will allow you to pull a report that will list Equipment Type, PM Type, Task, Parts, Labor Hours, etc per asset and per asset type.</p> <p><strong>Mission Critical</strong><br /> This is mission critical because it will assist managers when contractors have to submit re-competes for contracts. This information is vital because the contractors use this information to determine bidding on contracts for maintenance.</p> <p><strong>Benefits</strong><br /> This will benefit all activities in DPAS by reducing time, while allowing maintenance managers the ability to monitor and effectively manage the use and repair of equipment within their fleet.</p> <p><strong>Users</strong><br /> This should affect ALL users within DLA and DoD utilizing DPAS.</p>
20031Maintenance History01205PADLANewSubmitted: 9-6-2017<p><strong>Description</strong><br /> Problem: There's a need for a report that provided the history of the equipment to include labor hours, etc. The need is to review history of an individual piece of equipment.</p> <p><strong>Recommended</strong><br /> Develop a Maintenance History inquiry/report of equipment to include:  Asset ID, Estbd Dt, Work Order Id, DoD Serial number, Mfr Year, Mfr Name, Mfr Model Nbr, Item Desc, Requested Service, Work Plan Type, Service Performed, Current Mtr Rdng, Work Order Status Cd, Primary Tech, Labor Cost, Parts cost.</p> <p><strong>Mission Critical</strong><br /> This is mission critical because it will assist maintenance managers with workload planning and maintenance shop efficiency, along with maintenance history records for their activity.</p> <p><strong>Benefits</strong><br /> This will benefit all activities in DPAS by reducing time, while allowing maintenance managers the ability to monitor and effectively manage the use and repair of equipment within their fleet.</p> <p><strong>Users</strong><br /> This should affect ALL users within DLA and DoD utilizing DPAS.</p>
20030AD Hoc Inquiry01204MUDLANewSubmitted: 9-5-2017<p><strong>Description</strong><br /> Problem: Need an Inquiry/report that will allow selection of any field within DPAS and create an inquiry /report.</p> <p><strong>Recommended</strong><br /> Develop an AD Hoc inquiry/report that provides an opportunity to use multiple selectors...i.e., utilization, maintenance fields, custodian numbers, equipment pool, labor/non-labor cost, etc...to obtain information on the equipment at each UIC. Provide the capability to view Key Management Indicators that reflect the statistics for your equipment program to HQs.</p> <p><strong>Mission Critical</strong><br /> This is mission critical because it allows the DLA Activity Property Administrator the functionality to manage the and report information on equipment to higher leadership. It will also allow the leadership to have access to getting information without having to pull multiple reports from both modules.</p> <p><strong>Benefits</strong><br /> This will benefit all activities in DLA and potentially DoD by reducing time, while allowing Activity Property Administrator's the ability to monitor and effectively manage the use of equipment as well as optimize their fleet.</p> <p><strong>Users</strong><br /> This should affect ALL users within DLA and DoD utilizing DPAS.</p>
20029QC clear all inspection that are generated01203WarehouseAF: AFERMSDoneSubmitted: 6 Sept 2017<p><strong>Description</strong><br /> Click All button for canceling all generated self generated QCs, currently you have to select one at a time to cancel inspection</p> <p><strong>Recommended</strong><br /> When you click the All box make the Cancel button operate, once you click cancel, have a pop up that ask are you sure you want to cancel, yes or no</p> <p><strong>Mission Critical</strong><br /> desired</p> <p><strong>Benefits</strong><br /> time savings reduction of click major time savings, literally some warehouses have over 900 clicks to clear this area</p> <p><strong>Users</strong><br /> all</p> <p><strong>Completed – Release 6.0 – 12 January 2018</strong></p>
20028Container Inspection Request01202WarehouseAF: AFERMSNewSubmitted: 6 Sept 2017<p><strong>Description</strong><br /> We have sets in containers. we need the ability to sign off the inspections all at once instead of 120 individual inspections for containerized items. We also have individual container systems like mobility pallets that need inspections. We also would like to pick and choose Items with in the container to inspect or assign an inspection to. Aircraft as a container, has different equipment on it, we do post flight so that is one inspection. But all items within the container may have different dates.</p> <p><strong>Recommended</strong><br /> create an option to put an inspection against a container.  have that inspection apply to all items within the container. </p> <p><strong>Mission Critical</strong><br /> highly important.  we have mobility bins that are containers and require inspections.</p> <p><strong>Benefits</strong><br /> time savings.</p> <p><strong>Users</strong><br /> all users.</p>
20027Provide SA/LW Registry Reporting to Warehouse01201WarehouseSOCOMNewSubmitted: 8/25/2017<p><strong>Description</strong><br /> DPAS's Warehouse /  Materiel Mgmt modules currently do not report electronically to a Component or National SA/LW registry.  The Navy Registry located at CRANE, IN was not accepting electronic transactions, but is willing to consider an electronic feed based upon transactions that are processed.<br />  The DPAS PA Module currently interfaces with the Army Component / National Registry via it's UIT Interface with LOGSA, but it does not currently support the SA/LW accounted for within the Warehouse module.<br /> With USSOCOM looking to utilize the Warehouse module for weapons inventory and with SPECWARCOM migrating its weapons accountability to the Warehouse module (from SWALIS), there is a need to automate the reporting / reconciliation process to reduce the level of effort to maintain the registry and improve the overall reporting and speed I.E. perform the reporting using the actual transactions processed within the inventory system vs. manual documents that are generated by hand often times.</p> <p><strong>Recommended</strong><br /> Automate the SA/LW reporting for warehouse actions to the Navy Component Registry (P64).<br />  All receipts, issues, gains, and losses will be reported via the DLMS140A transaction set.<br />  Inventory adjustments (Stock Nbr / Serial Nbr changes) will be reported via the DLMS 888A transaction set.<br />  The implementation must be accomplished in a way that DPAS can accept registry 'transaction rejects' from the component registry (transactions that were sent to the registry for processing which were not accepted.<br />  The design should permit the user take the  necessary corrective action, and resubmit the transaction along with simultaneously correcting the user record in DPAS.<br />  This SCR also includes the requirement to be able to conduct reconciliations with the component SA/LW registry, and respond to registry follow-ups.</p> <p><strong>Mission Critical</strong><br /> This SCR is considered critical for the successful implementation of DPAS.  With USSOCOM planning to use the Materiel Mgmt/Warehousing modules to manage the wholesale inventory of weapons and related accessories that are subject to registry reporting, the level of effort to perform this manually is cost and resource prohibitive.</p> <p><strong>Benefits</strong><br /> Automating this process will improve reporting accuracy, and reduce the cost of reporting to the federal government.  Utilizing standard DLMS transactions should enable this interface to be used to feed the other component registries (Army  & Air Force), assuming they accept DAAS style transactions.</p> <p><strong>Users</strong><br /> The affected users are likely Navy, Marine Corps, and USSOCOM and their associated organizations report their SA/LW reportable items via the Navy Registry.  With validation/testing, the use of this capability could be expanded to other Service Registries.</p>
20026Add Condition Code to Custodian Asset Report01200PANavyRemovedSubmitted: 30 Aug 2017<p><strong>Description</strong><br /> The asset condition code is not on the Custodian Asset Report.  Verification of the assets condition is a requirement for Navy FIAR inventory efforts.  It is also required to keep the condition code updated in the APSR per SECNAVINST 7320.10A.</p> <p><strong>Recommended</strong><br /> Add condition code to the Custodian Asset Report.<br /> The condition code has been added to the custodian inventory report to support inventory requirements of DODI 5000.64 and SECNAVINST 7320.10a however recommend it also be added to the Custodian Asset Report.  After an inventory is conducted the Custodian Asset Report is provided to the custodian as documentation of assets in their custody.</p> <p><strong>Mission Critical</strong><br /> Not mission critical but a FIAR requirement, and SECNAVINST 7320.10A requires verification of condition code.</p> <p><strong>Benefits</strong><br /> Will improve custodian's ability to view the current condition of assets in DPAS to meet the SECNAVINST 7320.10A requirement.</p> <p><strong>Users</strong><br /> Yes to all Agencies</p> <p><strong>21 Aug 2019 – cancelled per Kevin Callahan </strong> <br /> No Longer Required.</p>
20025TCTO (Time Compliance Technical Order)01199WarehouseAF: AFERMSDoneSubmitted: 30 Aug 2017<p><strong>Description</strong><br /> We have one time inspections called TCTOs (Time Compliance Technical Orders) that are required to be accomplished on items.  these items have a completion date assigned that can range from immediately (which renders the item in-serviceable until it is accomplished), to next inspection cycle which allows the item to be used as is until the next scheduled inspection.</p> <p><strong>Recommended</strong><br /> create an inspection type of TCTO that can be assigned to an NSN.  give a field for compliance date.  if the inspection is not completed by the compliance date downgrade to condition "F". this inspection needs to be assigned to all items of the affected NSN to include items that are in kits and items that are issued.  we need to be able to sign off the inspection even if the item is in a kit without first having to remove the item from the kit.</p> <p><strong>Mission Critical</strong><br /> critical.  this involves safety of flight in some instances.</p> <p><strong>Benefits</strong><br /> we can auto-generate a TCTO inspection on items and mandate completion even if the item is kitted, signed out, or both.</p> <p><strong>Users</strong><br /> all AF users.</p> <p><strong>Partially Completed – Release 6.3 – 21 December 2018</strong></p> <p><strong>Completed – Release 7.0 – 20 April 2019</strong></p>
20024serviceable storage01198WarehouseAF: AFERMSDoneSubmitted: 30 Aug 2017<p><strong>Description</strong><br /> We have equipment that is put into serviceable storage similar to WRM (war reserve material). This equipment has some inspections waived until put into full service. there is no way to currently handle this material.</p> <p><strong>Recommended</strong><br /> create a location type of "serviceable storage".  create check box that is selectable when assigning an inspection to an item to declare that this inspection is conducted when an item is placed into this location type. all other inspection types will be deactivated when placed in serviceable storage.</p> <p><strong>Mission Critical</strong><br /> highly important.  We cannot handle equipment that will soon be loaded into the system.  It will generate inspections that are not due.</p> <p><strong>Benefits</strong><br /> will have accurate inspection due list.</p> <p><strong>Users</strong><br /> AFERMS plus more users of WRM material</p> <p><strong>Completed – Release 7.0 – 20 April 2019</strong></p>
20023MRO Due In01197WarehouseAF: AFERMSNewSubmitted: 30 Aug 2017<p><strong>Description</strong><br /> We have testers that are sent off installation for contract calibration.  the MRO process allows us to release these items but we then have to create a due in to gain the items back.</p> <p><strong>Recommended</strong><br /> create a check box in the MRO to auto generate the due in for the MRO</p> <p><strong>Mission Critical</strong><br /> important.  reduces work and ensures the due in is created</p> <p><strong>Benefits</strong><br /> no loss of accountability of equipment</p> <p><strong>Users</strong><br /> all AFERMS users possibly all users</p>
20022IMDS (Integrated Mechanical Diagnostics System)01196WarehouseAF: AFERMSNewSubmitted: 30 Aug 2017<p><strong>Description</strong><br /> IMDS (Integrated Mechanical Diagnostics System) is the source database for combat aircraft maintenance. we are required to use this database to track aircraft parts and components. the survival kits and parachutes we maintain for these aircraft are tracked in IMDS. we are double documenting if we track in DPAS and IMDS</p> <p><strong>Recommended</strong><br /> have DPAS talk to IMDS</p> <p><strong>Mission Critical</strong><br /> mandated. we have to use IMDS to track aircraft components</p> <p><strong>Benefits</strong><br /> updating one system instead of two</p> <p><strong>Users</strong><br /> all AFERMS users</p>
20021default completion time01195WarehouseAF: AFERMSNewSubmitted: 30 Aug 2017<p><strong>Description</strong><br /> there is a function to track time to compete inspections.  we need default times assigned to NSNs. If time is greater than the default a justification narrative needs to be input.</p> <p><strong>Recommended</strong><br /> add field at the NSN level to input default inspection time. when an inspection is performed that has a default time, mandate a start time and auto-populate a stop time.  allow adjustment of the stop time.  if the stop time exceeds the default inspection time, require a justification narrative be input.</p> <p><strong>Mission Critical</strong><br /> mandated.  tracking time to perform inspections allows AFE to justify manpower positions</p> <p><strong>Benefits</strong><br /> manpower justified</p> <p><strong>Users</strong><br /> all AFERMS users</p>
20020GACP (global ammunition control point)01194WarehouseAF: AFERMSNewSubmitted: 30 Aug 2017<p><strong>Description</strong><br /> GACP (global ammunition control point) is to munitions what JACKS is to CBRNE.  We need GACP to automatically update suspended munitions lots</p> <p><strong>Recommended</strong><br /> have DPAS talk to GACP</p> <p><strong>Mission Critical</strong><br /> important. eliminates human error</p> <p><strong>Benefits</strong><br /> eliminates human error in updating suspended munitions</p> <p><strong>Users</strong><br /> all users of munitions</p>
20019consumable components01193WarehouseAF: AFERMSNewSubmitted: 30 Aug 2017<p><strong>Description</strong><br /> we have smaller components (nuts, bolts, zip-ties, etc) that we would like to track, but cannot add undue burden of adding and removing these components to kits. We need a component category of consumable</p> <p><strong>Recommended</strong><br /> add a check box to the SKO edit grid "consumable" to denote an item is a consumable. In add another column, that is required if this is selected, "default qty consumed". In the QC/Insp "manage" button grid. add a consumable components tab.  each consumable line should have a check box to take the default number and a qty picker to adjust it if necessary. when the inspection is completed the inventory levels should be adjusted down the amount consumed.</p> <p><strong>Mission Critical</strong><br /> required to track all stock in a warehouse</p> <p><strong>Benefits</strong><br /> we can use DPAS as the sole inventory system for all stock items in a warehouse</p> <p><strong>Users</strong><br /> all users</p>
20018editable expiration dates01192WarehouseAF: AFERMSDoneSubmitted: 30 Aug 2017<p><strong>Description</strong><br /> We have items that have variable expiration dates.  some batteries last longer than the advertised expiration date in FEDLOG.  survival modules and medical modules do not have expiration dates that are exact to the shelf life code in FEDLOG (it's more of a ball park expiration date).</p> <p><strong>Recommended</strong><br /> allow editing of the expiration date. the expiration date should auto-calculate off the shelf life code, but be an editable field.</p> <p><strong>Mission Critical</strong><br /> critical.  we are currently having to hand write the actual expirations on forms and ignore the condition codes assigned to items that show as expired in DPAS.</p> <p><strong>Benefits</strong><br /> accurate condition codes of items</p> <p><strong>Users</strong><br /> all users</p> <p><strong>Completed – Release 6.0 – 27 April 2018</strong></p>
20017duplicate member profiles01191WarehouseAF: AFERMSDoneSubmitted: 30 Aug 2017<p><strong>Description</strong><br /> when personnel are issued an item, the CAC is scanned, the search function searches their EDI PI number. If the number is not found it allows you to add the member.  We have many members that are added with a place holder number until their EDI PI can be added when they come into our office. this creates a duplicate of the member.</p> <p><strong>Recommended</strong><br /> if the EDI PI is not found have the search function move to last name and similar first name of members with EDI PIs starting with "ID" (the place holder identifier).  allow the user to select a profile to update or create a new profile if the found profiles are not correct.</p> <p><strong>Mission Critical</strong><br /> highly desirable</p> <p><strong>Benefits</strong><br /> will eliminate duplicate member profiles</p> <p><strong>Users</strong><br /> all users</p> <p><strong>Completed – Release 2020.2 – 26 June 2020</strong></p>
20016CAC scan issue01190WarehouseAF: AFERMSNewSubmitted: 30 Aug 2017<p><strong>Description</strong><br /> Issue of NVGs and other preflight gear needs to happen near instantaneously.  their are Lean Six Sigma events held to reduce preflight preparation.  any increase in time is not acceptable. </p> <p><strong>Recommended</strong><br /> allow scanning of CAC and then the item being issued.  Scanning of CAC is implying signature since the CAC is an item that is not supposed to be left unsecured.  under material mgmt, individual: add screen "CAC scan issue" . scan CAC then scan item. this should complete the transaction.  allow the transactions to queue and process as connectivity allows while permitting multiple transactions to occur before processing.</p> <p><strong>Mission Critical</strong><br /> critical to use the system for signing out NVGs and other preflight gear.</p> <p><strong>Benefits</strong><br /> we can use the system for preflight issue</p> <p><strong>Users</strong><br /> all AFERMS users</p>
20015API01189WarehouseAF: AFERMSDoneSubmitted: 30 Aug 2017<p><strong>Description</strong><br /> There is no field on UICs to assign an API (Aircrew Position Indicator). This number shows authorized quantities of equipment.</p> <p><strong>Recommended</strong><br /> add numeric field to UIC "API"</p> <p><strong>Mission Critical</strong><br /> critical</p> <p><strong>Benefits</strong><br /> reference data to justify equipment will be available in system</p> <p><strong>Users</strong><br /> all AFERMS users</p> <p><strong>Completed – Release 6.0 – 27 April 2018</strong></p>
20014100pcnt 3 lvl QC01188WarehouseAF: AFERMSDoneSubmitted: 30 Aug 2017<p><strong>Description</strong><br /> 3 level personnel require 100% QC on tasks that they are not certified on in their training records.  We require a function to automatically generate these QCs</p> <p><strong>Recommended</strong><br /> on "Personnel" edit grid.  add a field to add stock numbers. If a stock number is added in this field a QC should automatically be generated when an inspection is completed with the personnel assigned.</p> <p><strong>Mission Critical</strong><br /> important.  ensures 100%</p> <p><strong>Benefits</strong><br /> assurance that members are getting 100%QC</p> <p><strong>Users</strong><br /> assurance that members are getting 100%QC</p> <p><strong>Completed -- Release 2021.2 - 28 May 2021</strong></p>
20013QC creation extra clicks01187WarehouseAF: AFERMSNewSubmitted: 30 August 2017<p><strong>Description</strong><br /> when adding an inspection there are extra clicks</p> <p><strong>Recommended</strong><br /> after adding the stock number (which we should be able to scan to)clicking next button we should not have to click select items to get the grid to populate.  this should be a gimme when we click next.</p> <p><strong>Mission Critical</strong><br /> desired</p> <p><strong>Benefits</strong><br /> time savings reduction of click</p> <p><strong>Users</strong><br /> all</p>
20012Enterprise Fleet Dashboard Access01186MUOSDDoneSubmitted: 30 Aug 2017<p><strong>Description</strong><br /> Currently there is no dashboard reflecting Total Fleet Operations within DPAS at a glance.  Would require access at the Enterprise Level for the DoD FM, Agency Level for Agency FM and Maintenance Level for the Area FM.  Same type of information at each level controlled by level of access.</p> <p><strong>Recommended</strong><br /> Dashboard information in ledger and graph similar to Dispatch for the following.<br />  Should be able to drill down to asset and refreshing.</p> <ul> <li>Total FAST Reportable # (# owned, # GSA, # Commercial - <i>Pie Graph</i>)</li> <li>Total FAST Reportable # (# profiled and # profiled - <i>Pie Graph</i>)</li> <li>Total # Maint Asset Util = 0 - Total # Fuel Util = 0</li> <li>Total # Cost = 0 - Utiliztion Tracking (# 12-9K miles, # 8.9K3k, # 290 - <i>Pie Graph</i>)</li> <li>Cost (Lease, Maint, Accident Repair - <i>Pie Graph</i>)</li> <li>Vehicle Type - <i>Pie Graph</i></li> <li>Vehicle Fuel Type - <i>Pie Graph</i></li> </ul> <p><strong>Mission Critical</strong><br /> Mission critical.  Will utilized to maintain EO compliance and FAST Data validation.</p> <p><strong>Benefits</strong><br /> Improves Fleet Operations by having FAST Data visibility constantly.  Reduces time by having available on dashboard to access graphs for briefs.</p> <p><strong>Users</strong><br /> Currently Fleet for now but expandable for other commodities in M&U</p> <p><strong>Completed – Release 6.3 – 21 December 2018</strong></p>
20011Existing Open Work Order message01185MUAF: VSCOSDoneSubmitted: 8/9/2017<p><strong>Description</strong><br /> When a user is opening a new Work-order but there is currently one already opened there is no way of informing the user. We recommend that a warning message appears stating "there is already a existing open work-order for this asset." If the asset has one already. This will reduce the number of open main work-orders on a asset at one time and properly capture the work at the sub wok-order level if applicable.</p> <p><strong>Recommended</strong><br /> Add a message to inform user that there is already a open work order on the asset. The message should state the Work Order # and that its open in red. Message should flag after the add criteria screen. Or after you select the Asset Id and click select. The screen flashes when adding asset information, so the system should be checking for open work-orders as well.</p> <p><strong>Mission Critical</strong><br /> This is critical.  Fleet managers count on viewing information to be able to make informed decisions to manage Air Force fleets around the globe.</p> <p><strong>Benefits</strong><br /> This will reduce multiple work orders open on the same asset. This causes issue with the Air Force reporting mission capability of its assets. Having multiple work orders on an asset at the same time skews data. This will also aid in data integrity.</p> <p><strong>Users</strong><br /> This SCR will affect the entire AF Agency, to include other services.</p> <p><strong>Completed – Release 6.2 – 31 August 2018</strong></p>
20010All Sub Work Orders should inherit Closed State Code when entered on Main Work Order01184MUAF: VSCOSNewSubmitted: 8/9/2017<p><strong>Description</strong><br /> When closing work-orders once you change the state code to closed you have to go to each individual sub work-order and change the state code, this is time consuming. Especially if there are numerous sub work-orders, to include having to insert a Service End date.</p> <p><strong>Recommended</strong><br /> Recommend sub work-orders inherit the same work-order state code and the same return date (Service End Date) as the main work order. Also allow the user to change manually if need be.</p> <p><strong>Mission Critical</strong><br /> This is critical.  Fleet managers count on viewing information in a timely manner to be able to make informed decisions to manage Air Force fleets around the globe.</p> <p><strong>Benefits</strong><br /> Benefits would include reducing transaction time when closing work orders and entering dates and the accuracy of the dates entered.</p> <p><strong>Users</strong><br /> This SCR will affect the entire AF Agency, to include other services that use the M&U module.</p>
20009Auto fill all date fields from the Receipt Date input field and remove the Return Date field from the open work order screen01183MUAF: VSCOSNewSubmitted: 8/9/2017<p><strong>Description</strong><br /> During the new work-order process; a user has to input dates multiple times and in multiple blocks. Having the ability to only enter the date once improves time when entering information. Also, the Return Date block from the open Work-Order basic screen should not be available in the open screen.</p> <p><strong>Recommended</strong><br /> Recommend that 2 other date fields (Avail, & Approval Dt) auto fill when the user inputs the date in the Receipt Date field. Also, remove the Return Date field until the user changes the Work Order Status Cd to C-Closed.</p> <p><strong>Mission Critical</strong><br /> This is critical.  Fleet managers count on viewing information in a timely manner to be able to make informed decisions to manage Air Force fleets around the globe.</p> <p><strong>Benefits</strong><br /> Benefits would include reducing transaction time when entering dates and accuracy of the dates entered.</p> <p><strong>Users</strong><br /> This SCR will affect the entire AF Agency, to include other services that use the M&U module.</p>
20008Address fields available in Inquiries, add an Address Inquiry01182MUAF: VSCOSNewSubmitted: 8/8/2017<p><strong>Description</strong><br /> When doing inquiries on Equipment Pools, Maintenance Officers, and Destinations not all information inputted into these fields are viewable or search-able by using the fields tab when setting up an Inquiry.  Addresses and remarks for example; the user cannot see what is current unless going to each one.</p> <p><strong>Recommended</strong><br /> Add Address field information to be available to be searched in Inquiries. Create a Inquiry to be able to search for addresses of Equipment Pools, Maintenance Officers, and Destinations. Create a Address Inquiry in M&U like the one in PA</p> <p><strong>Mission Critical</strong><br /> This is critical.  Fleet managers count on viewing information to be able to make informed decisions to manage Air Force fleets around the globe.</p> <p><strong>Benefits</strong><br /> Allowing addresses to be viewed in Inquiries will enhance reports and inquiries for all. Enabling user to be able to find any information on customers. This will aid in data integrity.</p> <p><strong>Users</strong><br /> This SCR will affect the entire AF Agency, all Air Force fleet managers/maintenance controllers utilize this information for day to day fleet management purposes.  </p>
20007Catalog Stock Number Field01181WarehouseAF: VSCOSNewSubmitted: 03/28/2017<p><strong>Description</strong><br /> The Add Stock Number field does not allow any special characters and it is limited to only 15 characters in length. Many vehicle manufacturers and commercial vendors utilize special characters in their part numbers. The current DPAS Warehouse add stock number field parameters make it very difficult for these vehicle part numbers (that are not NSNs) to be inputted into DPAS. When changes are made to make these part numbers fit such parameters, the entire part number is changed and no longer a valid manufacturer part number.</p> <p><strong>Recommended</strong></p> <ol> <li>Open the add stock number field to accept as a minimum these special characters "-", ".", "/",</li> <li>Accept up to 25 characters in length.</li> </ol> <p><strong>Mission Critical</strong><br /> It is mission critical to be able to find the correct part number for vehicles being maintained. If correct part numbers are not found/used this in turn could lead to wrong parts being ordered, used and ultimately could cause safety mishaps. </p> <p><strong>Benefits</strong><br /> Allowing for special characters and increasing the length of the stock number will enable for more accurate parts research and decrease the chances of wrong parts being ordered and used. Utilizing the correct parts will save money and increase the safety and serviceability of vehicles.</p> <p><strong>Users</strong><br /> This change will positively impact not only Air Force users but all DPAS Warehouse users as well.</p>
20006Individual Return Queries01180WarehouseUSMC: CSPRemovedSubmitted: 17 Aug 2017<p><strong>Description</strong><br /> Currently DPAS-WM does not have the option to use My Queries during an Individual Return.  Recommend that My Queries functionality be added to the Individual Return process.</p> <p><strong>Recommended</strong><br /> Recommend that My Queries functionality be added to the Individual Return Process. </p> <p><strong>Mission Critical</strong><br /> Yes, this will help increase the speed and proficiency during the Individual Return Process. </p> <p><strong>Benefits</strong><br /> Having this functionality will help with the speed and proficiency during the individual return process.  thus being able to get more members through the Individual return Process.</p> <p><strong>Users</strong><br /> All IIF</p> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
20005Add new CIP GLAC - 1516 - Operating Materiel & Supplies - In Development01179PALeidosNewSubmitted: 8/17/2017<p><strong>Description</strong><br /> Auditors have identified the need to have a Construction In Progress Account for Operating Materials and Supplies.  The U.S. Treasury has added GLAC 1516. This GLAC will permit those agencies that "construct" OM&S items, such as a missile which may take several years for the delivery to occur.</p> <p><strong>Recommended</strong><br /> Add new Asset Cd and GLAC to the CIP Project process and various DPAS Inquiries, CFO / Trial Balance reports.  Coordinate change with financial systems to determine if they can accommodate the new Asset Cd.  If they are not able to, identify the Asset Cd this account should be mapped to.</p> <p><strong>Mission Critical</strong><br /> This is a policy change that DPAS needs to implement as it has customers that construct OM&S material.</p> <p><strong>Benefits</strong><br /> No other known work around to identify OM&S in Construction.</p> <p><strong>Users</strong><br /> This change is limited to those customers that construct OM&S which requires it to be managed through CIP.</p>
20004Incorporate Materiel Returns Program into Materiel Mgmt, Warehouse, and PA modules01178EnterpriseSOCOMNewSubmitted: 8/14/2017<p><strong>Description</strong><br /> USSOCOM is transitioning a number of its logistics processes from multiple systems, and in some instances manual processing to DPAS as it looks to integrate with its supported Service Special Operations Commands (SOCs).  Several of the Army's PEOs is also looking to use DPAS to support the fielding of new equipment.  These transitions will likely encompass the use of all modules of DPAS.  One the processes that DPAS does not currently support is the DoD's Materiel Returns Program (MRP).</p> <p><strong>Recommended</strong><br /> DPAS needs to incorporate the requesting / management of a Materiel Return into the PA and Warehouse modules.  <br />Within the Materiel Mgmt module, DPAS needs to incorporate the acceptance, determination and response of the request.  Each Module should provide the user with the a viewer of the request along with the response provided. For "Accepted" materiel returns to the DPAS internal Materiel Mgmt module, the Materiel Mgmt module should generate and send a 527D (Due In) to the RSA (DPAS or an external RSA). This SCR encompasses the need for inquiries/reports to show the open items as well as closed actions with the actual disposition taken.  <br />Dashboards displaying open actions in the PA, Warehouse and Materiel Mgmt modules should be developed along with the capture of metric showing the number of approved/denied disposition of the MRP Request.  Programs that can be executed by the user that identifies potential excess equipment and supplies is recommended utilizing Authorized to On Hand quantities for PA.  <br />For the Warehouse module, the system should utilize Program Exit Dates (item no longer used), Demand quantities (is stockage too high for the current demand), and should also look at the Unit's Authorized to Issue Qtys.  For items considered excess, that are subject to return the ICP, the system will generate a DLMS 180M (Return Merchandise Authorization and Notification)transaction set to the Item Manager.  Responses to the DLMS 180M will be via the DLMS 870M (Materiel Returns Supply Status) transaction Set.  For additional guidance, refer to DLM 4000.25, Volume 2.</p> <p><strong>Mission Critical</strong><br /> Yes.  As DPAS increases its users base and expands the support of it Logistics Capabilities there is a requirement to support the DoD Materiel Returns Program for the Customer and for the Product Manager.</p> <p><strong>Benefits</strong><br /> Improves the overall integration with DoD programs.  Saves the Department $ as user may be more inclined to use the MRP, when the automation exists.  This capability is considered mandatory for the Materiel Manager as well as the user.</p> <p><strong>Users</strong><br /> As DPAS is used more within the Special Operating Forces environment, this capability will be used more an more.  The requirement was also listed in the USMC DMC Requirements package to support parts within the kitting area.</p>
20003Modify DPAS to support the Receipt and Mgmt of Customer Requisitions01177WarehouseSOCOMDoneSubmitted: 5/9/2017<p><strong>Description</strong><br /> USSOCOM is transitioning a number of its logistics processes from multiple systems, and in some instances manual processing to DPAS as it looks to integrate with its supported Service Special Operations Commands (SOCs).  This transition will likely encompass the use of all modules of DPAS.  One the processes that DPAS does not currently support is the receipt and management of Customer Requisitions (DLMS 511R), which is required as USSOCOM is a Source of Supply to the (SOCs) using the RIC of H9D.  The majority of the spare parts consumed by the SOCs are ordered today using the DoD Standard Supply Requisitioning Process. </p> <p><strong>Recommended</strong><br /> Incorporate the capability to accept a Customer Requisition (DLMS 511R) within the Materiel Management module of DPAS from a DAAS transmission.  Provide the user with a screen to view and manage (Review, Accept, Deny, Modify, Refer, Monitor) Customer Requisitions.  In addition to accepting the DLMS 511R, the system must be capable of supplying the customer with the status of their requisition via the DLMS 870S and to be able to accept modification, cancellation and status requests from the customer.  The process must be able to generate and submit a DLMS 940R to the Remote Storage Activity (RSA) that the item manager desires to have fill the requisition, to include being able to request and accept statuses from the RSA.  See attached document for additional information.<br /><em>Note: </em>This SCR does not include the capability to accept and manage Customer Return Requests as outlined in DLM 4000.25 / DLMS 180M Transaction Set.  Should this capability be required, a separate SCR will be submitted to request the incorporation of this functionality.</p> <p><strong>Mission Critical</strong><br /> Yes.  The SOCs order their consumables / repair parts using MILSTRIP procedures from USSCOM.  In order to fully transition to DPAS, the capability to accept a customer requisition is required.</p> <p><strong>Benefits</strong><br /> Provides for the reduction in the number of systems that USSCOM must use, thus improving the integrity of the information and reducing the total cost of operation.</p> <p><strong>Users</strong><br /> This SCR will benefit all users who have a requirement to accept and manage Customer requisitions using DPAS.  It may prove to be invaluable to the Air Force GFM-A effort, as they begin the transition of some of the CICPs to DPAS.</p> <p><strong>Completed – Release 6.2 – 31 August 2018</strong></p> <p><strong> Partially Completed -- Release 2021.2 - 28 May 2021</strong></p>
20002FAST Reportable Inquiry01176MUOSDNewSubmitted: 7/29/17<p><strong>Description</strong><br /> Mr. Sims (DoD FAST Manager) has requested DPAS Leidos personnel to execute a data extract monthly.  As such, it's only available when Leidos executes the database script.  If these output products are a required product of DPAS, they should be added to the menu as a standard inquiry, report or an Agency Pre-defined report.  The reports should have some filtering capability, thus the possibility of having these extracts as Agency Pre-defined may not be a viable solution. <br /> For example:  the ECC for trailers falls under ACC = P, but trailers are not FAST Reportable 'yet'.  I just want to ensure we all are on the same page on that.  This means, I need to have ECC = VU/VW omitted from the pulls and ensure we do not send those to FAST 'yet'.  Using the example, it appears that the reporting of trailers to FAST may be in the works, thus allowing the FAST Manager to include/exclude certain ECCs may be beneficial.<br /> Also, there are some scripts/pulls I will need at the Enterprise Level.  Do I do a SCR to have it created so I can pull in DPAS? <br /> These are the monthly reports I need reflecting FYTD and month totals:</p> <ul> <li>FAST Reportable in PA and M&U</li> <li>Maint Mgmt Cd = NPD</li> <li>Maint Asset Util <= 0</li> <li>Fuel Util not Reported</li> <li>Cost <= 0</li> </ul> <p><strong>Recommended</strong><br /> Migrate the current FAST database scripts from being limited to being executed by a Leidos person with Database Read Access to a menu selection allowing the user with the FAST Manager's role to request them as they require them.</p> <p><strong>Mission Critical</strong><br /> Any report that is a user report should not require a DBA to execute them.  The receipt of the reports is considered critical to the success of DPAS being able to accurately report to FAST.</p> <p><strong>Benefits</strong><br /> Eliminates the need for the FAST Manager to contact Leidos to execute the extracts each time they require them, as well as it eliminates the repeated receipt and running of the extracts by DPAS Leidos personnel.</p> <p><strong>Users</strong><br /> This report would be limited to user who are granted the FAST Reports.</p>
20001Manage Shelf Life By Expiration Date01175WarehouseSOCOMNew19 July 2017<p><strong>Description</strong><br /> The DPAS Warehouse module manages items subject to Shelf Life by CAGE, Mfr Contract, Mfr Lot and/or Mfr Date.  Medical items that are subject to Shelf Life are is often managed by Expiration Dt.  DPAS does not current support this method of knowing when an Item is no longer usable</p> <p><strong>Recommended</strong><br /> Recommend the Warehouse module's Shelf Life methodology include the capability to enter and manage by Expiration Date.</p> <p><strong>Mission Critical</strong><br /> Yes.  Without this capability, SPECWARCOM is unable to manage items that have a shelf life of an Expiration Dt.</p> <p><strong>Benefits</strong><br /> Does not require a separate to manage shelf life items that are managed by Expiration Dt</p> <p><strong>Users</strong><br /> All user and all organizations that have Shelf Life items that are supported by an Expiration Dt.</p>
20000Provide the Capability to Export the Pending Transactions Report in Excel01174PASOCOMDone13 July 2017<p><strong>Description</strong><br /> Currently the only option for printing the DPAS Pending Transactions Report is in PDF format.  USSOCOM would like to export this report in the excel format to allow for sorting to be better able to manage and reconcile the transactions.</p> <p><strong>Recommended</strong><br /> Provide the Pending Transaction Report to be exported in Excel Format.</p> <p><strong>Mission Critical</strong><br /> Mission critical to perform daily reconciliation of transactions performed.</p> <p><strong>Benefits</strong><br /> Tracking transactions in a timely fashion.  Improves accountability. </p> <p><strong>Users</strong><br /> All users within Agency.</p> <p><strong>Completed – Release 6.3 – 21 December 2018</strong></p>
19999Modify Document Nbr System Settings01173PASOCOMDone13 July 2017<p><strong>Description</strong><br /> Today DPAS sets the way Document Nbrs are managed at the Agency Level.  With USSCOM being a joint command, it provides support to all Services, thus the individual Service components have different requirements for Document Nbr Management.</p> <p><strong>Recommended</strong><br /> Modify the level in which Document Nbr mgmt is maintained, and / or allow it to be flexible to support Agencies that are Joint where the Document Nbr requirements vary.</p> <p><strong>Mission Critical</strong><br /> Mandated</p> <p><strong>Benefits</strong><br /> This is required for Army components.</p> <p><strong>Users</strong><br /> This will affect Army Components under SOCOM Agency as well as give other components the option to produce document numbers for updates.</p> <p><strong>Completed – Release 6.3 – 21 December 2018</strong></p>
19998Interface with SOCOM's SOLMAN Application for Authorization and Catalog Data01172PASOCOMNew13 July 2017<p><strong>Description</strong><br /> USSOCOM maintains unique Catalog and Authorization data in our Special Operations Logistics Management System "SOLMAN" application.  With USSCOM transitioning their Logistics Property Accountability and Warehouse operations to DPAS, there is a requirement to have this information available within DPAS to support these functions.  </p> <p><strong>Recommended</strong><br /> The solution is to provide a level of integration of DPAS and SOLMAN data.  There is a need for a joint DPAS / SOLMAN team to review the data and identify the level of integration that can best be obtained and how best to provide that level of integration (interfaces, web services, direction and type).  The design should support stand alone and well as enterprise DPAS sites.</p> <p><strong>Mission Critical</strong><br /> Mandated</p> <p><strong>Benefits</strong><br /> As USSOCOM transitions Requisition Mgmt to DPAS, there is a requirement to identify whether the unit placing the requisition has a requirement for the item.  Sharing Catalog data will improve accuracy and reduce the amount of effort to catalog an item.</p> <p><strong>Users</strong><br /> This will affect the catalog division of SOCOM Agency as well and provide a process for electronically providing / maintaining authorization data.</p>
19997Improve Visibility of Pending Transactions01171PASOCOMDone13 July 2017<p><strong>Description</strong><br /> There is no notification in the message box that informs APO/PA of incoming transactions.  The current design of Pending Transactions also makes it difficult to know if there are transactions as you have to check each type of Pending Transaction to know if any exists.</p> <p><strong>Recommended</strong><br /> Add Pending Transactions to Action List.  Consider developing an email notification system where users can subscribe to specific notifications for a given UIC, Accountable UIC, Site, etc.  Modify how the Search Criteria for Pending Transactions works.  Consider providing users with the ability to view "All" Pending Transactions at once, in addition to specific types.  </p> <p><strong>Mission Critical</strong><br /> Mandated</p> <p><strong>Benefits</strong><br /> Improves accountability and provides units notification of incoming property.   Reduces the level of effort to know when pending actions exist. </p> <p><strong>Users</strong><br />Affects all Agency when performing transactions within DPAS.</p> <p><strong>Completed – Release 6.2 – 31 August 2018</strong></p>
19996Mass Mgmt of Addresses01170PASOCOMNew13 July 2017<p><strong>Description</strong><br /> DPAS manages addresses at the UIC level. Often times addresses are applicable to all UICs within an Accountable UIC, or Site, or Agency and in some instances they would be applicable to all of DPAS "Enterprise". The establishment/maintenance of addresses by UIC is very time consuming.  DPAS should permit Addresses to be established at a higher level e.g. Agency or Site or Accountable UIC, and allow subordinate activities (UIC) to use them.  This SCR is being submitted by Leidos DPAS at the request of USSOCOM.</p> <p><strong>Recommended</strong><br /> The recommended solution would be to allow Addresses to be established at higher levels that the UIC level, and allow them to be 'sharable' with lower levels within the organization tree, thus eliminating the need to manage identical addresses across the enterprise.</p> <p><strong>Mission Critical</strong><br /> This is SCR is a recommendation to reduce the level of effort to manage Address information.  While Addresses can be managed today as is, the process requires many more resources than necessary.</p> <p><strong>Benefits</strong><br /> This SCR will significantly reduce the resources required to manage Address information.  By being able to assign a specific individual(s) to manage Addresses rather than having everyone at all levels be responsible for keeping up with changes will improve accuracy as well.</p> <p><strong>Users</strong><br /> Yes, as well as all Agencies.</p>
19995Export Monthly Depreciation Report to xls.01169PANavyNewSubmitted: 23 June 2017<p><strong>Description</strong><br /> The Monthly Depreciation Report only exports as a PDF but Navy needs the option to export it to XLS to better support Navy Financial Improvement and Audit Readiness efforts. </p> <p><strong>Recommended</strong><br /> Add capability to export the Monthly Depreciation Report in XLS format.</p> <p><strong>Mission Critical</strong><br /> mission critical for FIAR support.</p> <p><strong>Benefits</strong><br /> Improves financial reporting analysis</p> <p><strong>Users</strong><br /> yes</p>
19994Improvement Inquiry01168PANavyNewSubmitted: 23Jun2017<p><strong>Description</strong><br /> Current Inquiry/Accounting/Improvement process does not permit you to filter by Site ID / Accountable UIC or add those fields to the extract file.  Currently if you use the wild card it extracts all improvements but no way to identify which Site ID they belong without considerable manual effort to look up the UIC to Site ID association.</p> <p><strong>Recommended</strong><br /> Add Site ID and Accountable UIC as a filter to the Inquiry/Accounting/Improvement process.  Also add Site ID and Accountable UIC to the fields for selection to be included on the output file.</p> <p><strong>Mission Critical</strong><br /> Navy is focusing on financial accounting and it is important to be able to extract improvement files and associate them to specific Site ID/Accountable UICs.  Navy has 14 Site IDs in DPAS. </p> <p><strong>Benefits</strong><br /> improves financial reporting / accounting.</p> <p><strong>Users</strong><br /> Yes,</p>
19993VAM Report01167MUDLANewSubmitted: 06-22-2017<p><strong>Description</strong><br /> Problem: There's no report that supports gathering all of the necessary data to perform a VAM Survey. There are multiple reports that are gathered together to develop one extremely long report for either a Contractor or Agency to have all of the necessary data to perform the analysis.</p> <p><strong>Recommended</strong><br /> Develop a report that will gather all of the pertinent information for the survey. The following fields are needed at a minimum:</p> <ul> <li>Report Year,</li> <li>Vehicle ID,</li> <li>Manufacturer,</li> <li>Model,</li> <li>Model YR,</li> <li>GVWR,</li> <li>Vehicle Type,</li> <li>Fuel Type Configuration,</li> <li>Location withheld,</li> <li>Garage Zip,</li> <li>Garage Lat.,</li> <li>Garage Long.,</li> <li>Acquisition date,</li> <li>Ownership type,</li> <li>Disposal date,</li> <li>Disposal reason,</li> <li>EPAct Coverage Designation,</li> <li>EPAct 2005 section 701 Designation,</li> <li>EISA section 141 Designation,</li> <li>EO 13693 Designation,</li> <li>LGHG Vehicle Qualifying as AFV,</li> <li>LE Designation,</li> <li>ER Designation,</li> <li>Armored Designation,</li> <li>Acquisition Cost,</li> <li>Miles traveled,</li> <li>Lease Cost,</li> <li>Maintenance Cost,</li> <li>Accident Repair Cost,</li> <li>Indirect Cost,</li> <li>Disposal Cost,</li> <li>Disposal Proceeds,</li> <li>Vehicle Comment</li> </ul> <p><strong>Mission Critical</strong><br /> This is mandated. Federal Management Regulation (FMR) 102-34.50 requires that executive agencies establish and document a structured vehicle allocation methodology (VAM) to determine the appropriate size, number, and types of motor vehicles.</p> <p><strong>Benefits</strong><br /> This will benefit all activities in DPAS to include DLA by reducing time.</p> <p><strong>Users</strong><br /> This should affect ALL Agencies utilizing DPAS.</p>
19992Attaching Documents in a Pending State01166PAMDANew01June2017<p><strong>Description</strong><br /> Designated assets will not allow a completed signed document to be attached at the Pending Approval page of DPAS when assets are dispositioned out of DPAS.  The challenge is attaching a document after "approve" has been select for a a dispositioned asset.</p> <p><strong>Recommended</strong><br /> Please allow a document to to be attached before the approved button is selected at the Pending Approval page in DPAS.</p> <p><strong>Mission Critical</strong><br /> Critical.  The documents signed by an outside DPAS agency are difficult to attach after the process is approved in the pending state.  Attaching a document should be completed before approving the transfer is complete.</p> <p><strong>Benefits</strong><br /> Improves/Accuracy/Accountabililty</p> <p><strong>Users</strong><br />All users</p>
19991Additional MU Fields For Inquiry01165MUMDANew01June2017<p><strong>Description</strong><br /> The "work order state" or "work plan type" are not displayed as a selection when selecting inquiry extract fields.  These should be available for viewing in an extract when an inquiry is completed.</p> <p><strong>Recommended</strong><br /> When creating the initial work order the "work order state" and "work plan type" are a part of the process.  Please make these fields available when selecting fields in an inquiry.   These fields should be viewable when the inquiry is complete.</p> <p><strong>Mission Critical</strong><br /> This is a critical as the customers are requesting the status of equipment.  The ability to print this information will be beneficial to the the DPAS user and customer as well.</p> <p><strong>Benefits</strong><br /> Improves/Accuracy/Accountablility</p> <p><strong>Users</strong><br /> All M&U users.</p>
19990Unable to send attachments to MRO when assets allocated..(completed in QC)01164MUUSMC: DMCRemovedSubmitted: June 01, 2017<p><strong>Description</strong><br /> Proposed Improvement: DMC (USERS) - Request Leidos Developers to add a new feature where, during the WH QC work order request process, an attached file is not only attached to QC in WH, but is also sent along with the QC work order request to M&U.</p> <p><strong>Recommended</strong><br /> When sending assets to M&U from QC, QC's "Attachments" should also transfer to M&U.</p> <p><strong>Mission Critical</strong><br /> This is a mandated change due to the communication issue between QC and the M&U module in DPAS when sending work orders.  QC can send an attachment with the work order request to M&U but when M&U opens it the attachment is not with the request. QC does not have the ability to type in information on their COSIS form the only option they have is to specify the level of preservation for the asset and they have a special instruction box that fits a "limited amount of information".</p> <p><strong>Benefits</strong><br /> Benefits of implementing this solution would improve the accuracy of information being shared on particular assets. It is imperative that the communication channels within DPAS QC and M&U work both ways.</p> <p><strong>Users</strong><br /> All DMC users affected.</p> <p><strong>11 Mar 2021 – cancelled per Jack Sanders </strong> <br /> No Longer Needed.</p>
19989DPAS to FLIS Interface01163PANavyDone31May2017<p><strong>Description</strong><br /> DPAS currently has a monthly interface with FLIS to update DPAS catalog National Stock Numbers (NSNs).   Monthly interface is not timely as NSNs are added / updated continually in FLIS.</p> <p><strong>Recommended</strong><br /> FLIS has direct web services/interfaces that are provided by the FLIS Portfolio Data Warehouse (FPDW) to support a real time interface to update DPAS catalog NSN's.</p> <p><strong>Mission Critical</strong><br /> Mission support to provide improved FLIS data to DPAS catalog teams and could reduce the creation of MCN stock numbers in the Property Accountability Module/ Warehouse module.</p> <p><strong>Benefits</strong><br /> Improves the accuracy of stock number cataloging.</p> <p><strong>Users</strong><br /> Yes all DPAS users would benefit. </p> <p><strong>Completed – Release 7.0 – 20 April 2019</strong></p>
19988Priority Levels for MU and Warehouse Orders01162MUAir ForceDone30May2017<p><strong>Description</strong><br /> There is no priority system within M&U and Warehouse to differentiate orders placed. Build a priority system to allow manager/supervisors to prioritize orders made in M&U through Warehouse</p> <p><strong>Recommended</strong><br /> Create a system in M&U and Warehouse to allow technicians to prioritize orders.</p> <ul> <li>Priority 1: Emergency</li> <li>Priority 2: Critical</li> <li>Priority 3: Routine</li> <li>Priority 4: Deferred</li> </ul> <p>Build a priority box into the Parts Tab in the Sub Work Order with a drop down menu containing the above priority levels. Priority level needs to start in M&U and reflect in both M&U and Warehouse through out the entire requisition, replenishment  and receiving/approving processes and then back to M&U through the maintenance issue process.</p> <p><strong>Mission Critical</strong><br /> Mandated. IAW 5.15. General Information. A NMCS condition starts extraordinary supply action by Materiel Control. 5.17.4. The VFM/VMS makes a policy on which MICAP and NMCS conditions they want briefed on and how often. Also, set up a general procedure as to what is unsatisfactory status, thus requiring more action.</p> <p><strong>Benefits</strong><br /> Prioritizing orders will reduce the time required for vehicles with higher maintenance priorities to receive the parts needed, while avoiding vehicles with lower priorities from being worked first. While reducing time, this SCR will also enable supervisors and technicians to improve the accountability of parts ordered and help achieve better financial reporting by improving accuracy of information provided/extracted from the system.</p> <p><strong>Users</strong><br /> This System Change Request will affect all users in the AF component</p> <p><strong>Completed – Release 7.1 – 26 July 2019</strong></p>
19987MandU Reset01161MUAir ForceNew22May2017<p><strong>Description</strong><br /> In order to meet education requirements for AETC, each class will need to start from a zero based lined Maintenance Activity, with the corresponding PA assets displaying as NPD or Not Profiled.  Corresponding PA Site-IDs will be left as is.</p> <p><strong>Recommended</strong><br /> Develop script to be run at the schoolhouse's request prior to start of each class.</p> <p><strong>Mission Critical</strong><br /> This is a mandated requirement to maintain scholastic accreditation.</p> <p><strong>Benefits</strong><br /> This "reset" function will significantly reduce the time needed to set a Maint Activity to baseline for each Class.</p> <p><strong>Users</strong><br /> This will affect only users on DF-AETC and DF-AETC2 on the EXT TRAIN environment.</p>
19986CFO Detail Extract Establish Date01160PAUSMCNewSubmitted: 5/22/2017<p><strong>Description</strong><br /> Currently, in the CFO Detail Extract there is not an attribute "Establish Date."  This attribute incorporation will improve the accuracy of the extract report by ensuring the accurate population is in the CFO Detail Extract for the quarter/period.  The current issue is that if the CFO Detail Extract is including population which were processed after the quarter/period.</p> <p><strong>Recommended</strong><br /> The recommended solution would be to incorporate "Establish Date" into the CFO Detail Extract.</p> <p><strong>Mission Critical</strong><br /> Yes.  This is mission critical due to the issuance of quarterly USMC standalone financial statements.  The CFO Detail Extract is used to reconcile against the Agency CFO Accounting Statement Report for deriving financial values for personal property for the development of the financial statements.</p> <p><strong>Benefits</strong><br /> Reduces time/cost, improves, accuracy, accountability and financial reporting.</p> <p><strong>Users</strong>: Yes</p>
19985CFO Report Begin Date01159PAUSMCNewSubmitted: 5/22/2017<p><strong>Description</strong><br /> Currently, in the Agency CFO Accounting Statement Report there is not an option to pick a "Begin Date."  This option incorporation will improve the accuracy of the CFO Report by ensuring the accurate values are generated in the quarter/period.  The current issue is that the CFO Report does not have an option of picking a begin date.  The begin date is defaulted to the First Quarter of the Fiscal Year (For example, 10/01/2016).  The main issue arises when attempting to download the Second Quarter CFO Report.  The CFO Report is generated by using the begin date 10/01/2016, therefore, consolidates all Q1 and Q2 accounts and associated values for the quarter/period.</p> <p><strong>Recommended</strong><br /> The recommended solution would be to incorporate "Begin Date" into the Agency CFO Accounting Statement Report.</p> <p><strong>Mission Critical</strong><br /> Yes.  This is mission critical due to the issuance of quarterly USMC standalone financial statements.  The Agency CFO Accounting Statement Report accounts and values are used to reconcile against the Agency CFO Accounting Statement Report for deriving financial values for personal property for the development of the financial statements. </p> <p><strong>Benefits</strong><br /> Reduces time/cost, improves, accuracy, accountability and financial reporting.</p> <p><strong>Users</strong><br /> Yes</p>
19984Asset Visibility Data Feed01158WarehouseSOCOMDone12APRIL2017<p><strong>Description</strong><br /> USSOCOM is implementing DPAS along with SPECWARCOM, AFSOC, MARSOC and possibly other special operations.  With these implementations, there is a need by USSOCOM to maintain visibility of materiel/equipment that might not otherwise be provided.</p> <p><strong>Recommended</strong><br /> It is requested that DPAS provide a daily feed in a comma delimited or xml format containing data elements as outlined in the attachment.  USSOCOM will process the file and populate their their Total Asset Vis system (SOLMAN).</p> <p><strong>Mission Critical</strong><br /> Yes.  USSOCOM requires visibility of all of the their gear for readiness and replacement planning purposes.</p> <p><strong>Benefits</strong><br /> Without the information, there is no way for USSCOM to accurately report readiness or plan for replacement of outdated / worn gear.</p> <p><strong>Users</strong><br /> No.  The change would be limited to the SOCs since it is an Asset Visibility feed to USSCOM for SOC items.  Without the feed, USSCOM operates blindly or is forced to obtain manual extracts from each of the SOCs.</p> <p><strong>Completed – Release 6.2 – 31 August 2018</strong></p>
19983Enterprise roll up inquiry for M&U01157MUAF: VSCOSNewSubmitted: 05/15/2017<p><strong>Description</strong><br /> M&U does not have access to enterprise (Agency/Site) level inquiries</p> <p><strong>Recommended</strong><br /> Create an Enterprise level of inquiries for M&U just like the enterprise level reporting is offered in the Warehouse module.</p> <p><strong>Mission Critical</strong><br /> Although neither mission critical nor mandated, this level of inquiry will allow VSCOS access to information needed to manage the AF global fleet without having to resort to multiple inquiries to get information from multiple UIC/MA into a single report</p> <p><strong>Benefits</strong><br /> This solution ease user-ability and reduce hundreds of man-hours. It will also improve on the accuracy of reports produced by the Enterprise Fleet Management offices and enhance the overall Financial Improvement and Audit Readiness of the AF fleet.</p> <p><strong>Users</strong><br /> This System Change Request will not only benefit AF fleet management users, but also all users within DoD and federal fleets who require enterprise level reporting.</p>
19982No update for Closed Work Orders after 30 days01156MUAF: VSCOSNewSubmitted: 3/7/2017<p><strong>Description</strong><br /> Limit the time that Closed Work Orders can be updated. Currently, Closed Work Orders can be updated at anytime. A cap should be in place so users cannot delay in making updates/changes or correcting mistakes with Closed Work Orders.</p> <p><strong>Recommended</strong><br /> Cap the time that Closed Work Orders can be updated to 30 days. Allow for editing within those 30 days but not have to fully reopen the work-order. Option should be edit vs not reopen so the work-orders open/close times aren't affected.</p> <p><strong>Mission Critical</strong><br /> Mandated. By DoD Regulation 4500 and AFI 24-302 to be able to capture (Vehicle in Commission)VIC/Mission Capable (MC) rates...total time vehicle is in service.</p> <p><strong>Benefits</strong><br /> This will benefit data accuracy and accountability for the DoD organizations that track VIC/MC rates of the vehicle fleets.</p> <p><strong>Users</strong><br />All DoD fleet managers will be effected by this.  </p>
19981Add Open Time to Main Work-order01155MUAF: VSCOSDoneSubmitted: 31 Mar 2017<p><strong>Description</strong><br /> Add open time to Main Work-order.</p> <p><strong>Recommended</strong><br /> Add Open/Close time to the main work-order screen. DPAS would run of a 24hr clock and capture when a vehicle work-order actually is ready for maintenance (date and time).</p> <p><strong>Mission Critical</strong><br /> Mandated. Air Force Maintenance Activities are required to capture start date and time a vehicle is out of service. Regardless, of when it actually arrives to the Maintenance Activity.</p> <p><strong>Benefits</strong><br /> Capturing time allows the Maintenance Activity to account for NMCM hours. "NMCM HOURS" - Vehicle down for maintenance hours.  Calculated by adding NMCM hours on regular and minor maintenance (Drop in maintenance) work orders from the DPAS Vehicle Master Record. Rounded to the nearest whole hour.<br />24 hour clock example: 1:00 PM = 1300.  When DPAS calculates NMC, all ‘Available Hours’ are rounded to the nearest whole hour.  Example: A work order opened between 08:00 and 08:29 rounds back to 08:00. A work order opened between 08:30 and 08:59 rounds up to 09:00.<br />"Available Hours" - The total available hours calculated by taking the sum of 24 hours a day, times the number of days in the month, times the number of vehicles assigned to each fleet’s category/LIN. Available hours for vehicles picked up/transferred off site during the month will be based upon transaction date.</p> <p><strong>Users</strong><br /> Yes</p> <p><strong>Completed – Release 6.2 – 31 August 2018</strong></p>
19980Training & Overtime Indicator block next to Labor Hours01154MUAF: VSCOSDoneSubmitted: 3/7/2017<p><strong>Description</strong><br /> Currently you cannot annotate and track the type of Labor Hours that the technicians operating under using, i.e. normal, training or overtime.</p> <p><strong>Recommended</strong><br /> Add a "Training Box" and "Overtime box" on the Sub Work Order Labor Tab, that can be easily check. We have attached a screen shot of where the Training Box can be on the screen. The box would only be check if a technician is assisted by a someone in upgrade training. For example: Technician 1 is fully trained on the job however and he has a new airman (Technician 2) performing the job with him for the first time. Technician 1 would simply input his time for the job as usual, Technician 2 would also input his time as normal but would also check the Training Box to indicate that he/she was being trained during this time. These fields/boxes will also be searchable during any work-order and labor inquiries and would also passed over to the GCSS warehouse during ETL run.</p> <p><strong>Mission Critical</strong><br /> Mandated. To be differentiate between a technician doing work they are qualified on or work they are being trained on. Annotating training time is beneficial in several areas for us. One it provides another avenue to properly track individual and maintenance facilities training programs. Two it provides an abi