|
Member Site Password Login
|
01752
|
PA |
USMC |
New |
Description:
Currently the only way to enter the DPAS Member site is via Common Access Card (CAC). This presents a problem for Marines who don't have daily access to a computer to check their issues.
Recommended:
Have the ability to allow users to login into the member site with either their CAC or create a username and password they could associate with their accounts. This will allow Marines to access via mobile devices instead of needing to be on a desktop or laptop computer. This solution should allow the members to have the full access to the member site.
Mission Critical:
Yes, this allows Marines to access their accounts through multiple ways.
Benefits:
Implementing multiple ways to login into the Member site will improve the ability for Marines to login into their accounts whenever required. This reduces customers time it would take to create appointments or pull outstanding list.
Users:
Yes, any customer of the CSP who has an issue. |
|
Member Site Store Front
|
01751
|
PA |
USMC |
New |
Description:
Marines and Sailors place their orders for individual issued equipment only upon arrival at the Individual Issues Facility (IIF). This process creates a time burden on the customer & IIF associate and increases the opportunity for a return trip to the IIF due to equipment not in stock on the day of the initial visit. Overall, this current process decreases efficiency and increases labor costs to CSP.
Recommended:
Marines and Sailors place their orders for individual issued equipment only upon arrival at the Individual Issues Facility (IIF). This process creates a time burden on the customer & IIF associate and increases the opportunity for a return trip to the IIF due to equipment not in stock on the day of the initial visit. Overall, this current process decreases efficiency and increases labor costs to CSP.
Mission Critical:
This is a mission critical request. The fiscal constraints placed on the Marine Corps' Consolidated Storage Program necessitate streamlining issue/receipt processes. The implementation of an equipment ordering portal will reduce the overall cycle time of equipment issuing and return-trips due to equipment availability thereby reducing the overall labor costs for the program and Marine or Sailor wait time.
Benefits:
-Reduced labor cost
-Reduced service time
Users:
All users who user individual issues or returns activities |
|
2015_NSN IS and reference NSN
|
01750
|
Enterprise |
USAF |
New |
Description:
The current program logic on the FSM Auth On-hand report does not take into consideration stock numbers that are a 'related NSN'. This is causing the FSM Auth On-hand product to either identify these related NSNs as excess and the Master NSN as shortages when in fact these NSNs can be used in lieu of the other.
Recommended:
Additionally within the Asset Management Inquiry, include I&S and 'Related NSN' as part of the data pull
Mission Critical:
Mission critical- currently the report is indicating that there are several shortages and excess based on the current program logic. This is hindering the DAF ability to properly report readiness as outlined in the CJCSI 3401.02B Enclosure A
Benefits:
Improves accuracy of or readiness reporting of assets physically on hand that meet the mission requirements
Users:
ll users within the Agency
|
|
CDAS Equipment Asset Processing in DPAS
|
01749
|
PA |
USAF |
New |
Description:
Air Force is currently recording its COMSEC/Crypto Equipment asset transactions in CDAS; however, the AF is transitioning from CDAS to ILS-S in 2022. Once the transactions are recorded in ILS-S, the Air Force needs to provide those transactions to DPAS (most likely the Property Accountability module) for accountability and financial reporting. Currently, there are no capital assets in the population of COMSEC/Crypto equipment in CDAS.
Recommended:
Need DPAS to receive, process and store the image copies of the DLMS transactions associated with these equipment items sent from the ILS-S COMSEC/Crypto warehouse SRAN. These transactions will consist of receipts, issues, shipments, condition code changes, inventory adjustments and disposals. Any capital assets within this population of COMSEC/Crypto assets would follow the existing AF processes for capital equipment in DPAS. In addition, need DPAS to perform end of day/end of month reconciliation to ensure DPAS matches ILS-S. It is expected the population of DLMS transactions will include: 527R, 824R, 832N, 867I, 945A, 947I, 846P, 846R and 536L. Also, 527D and 856 transactions may be necessary to record due-ins and track shipments to/from the warehouse. The 832N would be used to add new stock numbers to the DPAS catalog; the transaction would include the NSN, the Manufacturer’s Part Number, serial number and other elements per the DODI 5000.64. Additional discussions between DPAS and ILS-S re: sending transactions to ADVANA will be required.
Mission Critical:
Asset accountability and financial reporting is mandated. Need by date is June 2022.
Benefits:
This would provide accountability and financial reporting for AF COMSEC/Crypto equipment assets managed by the AF CCSD personnel in San Antonio, Texas. This solution would comply with the AF’s policy directing DPAS as the AF’s APSR for Equipment.
Users:
This affects the COMSEC/Crypto warehouse users.
|
|
Warehouse Location Delete Option
|
01748
|
Warehouse |
USAF |
New |
Description:
Current system process prevents users from fully deleting a location within Warehouse when location associates to a record. After disassociating the record, the only option is placing location into "Inactive" status and location is still visible to user. Fully deleting location from the system requires a Helpdesk ticket submission for backend script execution.
Recommended:
Enable user level delete function after disassociating all records from the location allows users to select "Delete location" clearing warehouse and prevents unnecessary user visibility.
Mission Critical:
The ability to delete locations removes excess and unnecessary location/storage providing mission enhancement within the Warehouse
Benefits:
Improves accuracy and accountability of Warehouse operations, prevents receiving stock items to erroneous locations and eliminates additional time to correct errors.
Users:
Affects ALL users within our Component/Agency. |
|
Telematics Current Mtr Rd Option
|
01747
|
MU |
USAF |
New |
Description:
Current telematics file upload process captures distance reported from a select period and adds the value to the previous meter reading to capture the current meter reading. Using this process methodology fails to validate the accuracy of the previous meter reading and can lead to compounded errors if file upload continues. Telematics output files offer a data value for meter reading directly from the assets computer. Using this value ensures data integrity by eliminating human data entry and potential flaws.
Recommended:
Update the telematics file upload process to accept Current Meter Reading and not the current Distance value option. This process will log a Asset Utilization Transaction with an updated Current Mtr Rdg based on the value directly from the telematics file. Upload file using this method requires configuring the Telematics File template with the following headers; Vehicle Id (Asset Id), Rptd Dt, Current Mtr Rdng, Serial Nbr. Additionally, build validation check into the process to prevent the file uploading if the Current Mtr Rdg is negative in value compared to the previous meter reading within DPAS. This ensures user validates and corrects discrepancies prior to system data entry.
Mission Critical:
Mandated and critical. Having capability prevents erroneous data reporting into mandated sources (i.e., FAST). FAST reports included over 15,000 flags tied to utilization and mileage errors within DPAS. Using Telematics is the way forward eliminating errors and adjusting entry format streamlines interface for users ensuring accurate data entry.
Benefits:
Implementing this system change greatly improves DPAS data accuracy for FAST, sustainment budgeting and financial reporting.
Users:
This effects all M&U users within DF-VEHS along with other DoD agencies using DPAS as their Fleet Management Information System (FMIS). |
|
Open Actions_Remarks
|
01746
|
MU |
SOCOM |
New |
Description:
There is not a link option under the DPAS MU "Open Actions/Work Order" window to select Closed Work Orders to quickly generate a list of all closed work orders under the maintenance activity; additionally, the work order lists that are generated from the open actions links do not include the appropriate data fields to enable the user to easily identify which asset the work order is against and what repair/job it was opened for.
Recommended:
Add a link under the DPAS MU "Open Actions/Work Order" window for closed work orders, include the "Remarks" data field from the Work Order/Basic tab as one of the displayed data fields in the work order list (can be truncated some) and replace the "Asset ID" data field with the "Serial Nbr" data field (or add as an additional field) on the work order list so users can easily identify the craft hull number.
Mission Critical:
No
Benefits:
This solution will significantly reduce time for NSW DPAS MU users to navigate to the correct closed work orders to edit work order data fields with new or updated information.
Users:
Yes. All current NSW DPAS MU users are required to frequently update information in closed work orders. |
|
Forms_Reports excel export
|
01745
|
MU |
SOCOM |
New |
Description:
Reports scheduled under the Forms-Reports menu in the MU module can only be exported in .pdf file format. When scheduling reports, a drop-down menu is already present for selecting report format types, but the only option currently available is .pdf format. The Work Order report under Forms-Reports is the only MU report/inquiry that provides all work order and sub work order data elements in a single report. NSWC needs these data elements in excel format in order to conduct analytics on the maintenance data that is recorded in the system.
Recommended:
Modify the file format options for the reports generated within the Forms-Reports menu of MU to include the excel file format. Add the excel format option to the available options on the existing file format drop-down menu.
Mission Critical:
Yes. WARCOM N8 and the PEO-Maritime SOCOM PEO is required to calculate Mean Time Between Operational Mission Failures (MTBOMF) for NSWC combatant craft using data that is entered into the DPAS MU module via repair work orders. In order to calculate this metric from MU data the Work Order report needs to be available in excel file format.
Benefits:
The proposed solution will significantly reduce time in conducting data-manipulation of the currently limited MU reports in order to put the data in a usable format for performing analytics.
Users:
This problem affects all NSW DPAS MU users. |
|
UTIL Modification for Boat Engine Hours
|
01744
|
MU |
SOCOM |
New |
Description:
The current Utilization functionality available in the MU module is not sufficient to permit recording engine hours against boat assets. The current functionality only permits recording a single metered history for an asset, and only allows consecutively higher readings for each recording instance. This limitation does not permit NSW users to record engine meter readings for boats that have two engines, or to record a lower meter reading or "reset" the record when boat engines are replaced on an asset.
Recommended:
Maintain the current Utilization functionality within the MU work order/Utilization tab to record craft hull hours, but add the ability to assign engines to craft by engine serial number (or pull the components from PA if they are associated with the asset's record as serialized components) and to record engine hour meter readings in a work order for each assigned engine. Add this functionality similar to the way the Sub Work Order/Labor tab records labor hours for specific technicians (select engine by serial number from drop-down, enter current hour meter reading, click "Save", adds record as a row with current meter reading or updates existing record for a specified engine to current meter reading). When engines are replaced, record of previous engines that have been removed should remain associated with the parent asset's history, and a new engine should be added as a new row.
Mission Critical:
Yes. In order to record all required data elements of maritime asset maintenance and repair actions, MU work orders need to have the ability to record engine hours for each assigned engine in order to associate maintenance events appropriately to engine and craft age/run time.
Benefits:
The proposed solution would improve the accuracy and completeness of maintenance data elements that are collected for NSW maritime assets using the MU work order process.
Users:
This problem affects all current NSW DPAS MU users. |
|
DPAS SCR LMP FTAC Updates
|
01743
|
Enterprise |
Leidos |
New |
Description:
The disposition of equipment needs to have it GLAC posting updated to align with the US Treasury USSGL proforma entry for LMP. This applies to all GPP&E (Military and Non-Military).
Recommended:
For Asset K and T, Funded - map the X814 - Transfer Out of Accumd Deprn-Disposal to FTAC 4908. For Asset K and T, Unfunded - map the X814 - Transfer Out of Accumd Deprn-Disposal to FTAC 4934.
Mission Critical:
This is required to bring the USSGL posting into alignment for LMP - Army AWCF funds.
Benefits:
Will bring LMP into alignment with current US Treasury proforma entries.
Users:
This SCR applies to all AWCF users of LMP |
|
RabbitMQ Communication
|
01742
|
Enterprise |
Leidos |
New |
Description:
Enhance the communication protocols for RabbitMQ.
Recommended:
Implement enhanced communication protocols for RabbitMQ to improve message bus communication.
Mission Critical:
N/A
Benefits:
Improved communication of message bus.
Users:
all |
|
Identity Service
|
01741
|
Enterprise |
Leidos |
New |
Description:
Current handling of DPAS security is segregated per web app and a bridging process is required to authenticate to new web apps. DPAS needs a centralized technical approach to handle this authentication, manage user accounts and store user details across the enterprise.
Recommended:
Create an Identity service that is responsible for managing user accounts, storing user preferences and saving user queries that can be used in all modules of DPAS allowing all DPAS web apps to share implementation of user specific functionality.
Mission Critical:
N/A
Benefits:
Improved reliability and experience for all customers. Consolidation of customer data while sharing new functionality across modules. Elimination of legacy authentication processes.
Users:
Yes, this will affect all users that authenticate with DPAS or use shared functionality such as user preferences or saved queries in newly implemented portions of DPAS.
|
|
WO Remain Open for WO State Cds of Deferred
|
01740
|
MU |
USMC |
New |
Description:
The WO is updated to Closed when an of the WO State Cd of Deferred is selected and USMC wants it to remain open.
Recommended:
Do not update the Status of the WO to Closed for any of the below Deferred WO State Cd DEFA Deferred-Persl Not Avail, Rtnd to Cust DEFC Deferred-Awtng Mtrls, Rtnd to Cust DEFD Deferred-TCTO kit Rqd, Rtnd to Cust DEFF Deferred-Cntrct Repair, Rtnd to Cust DEFG Deferred-Excds One Tm Rpr Limit (OTRL), Rtnd To Cust DEFH Deferred-Skillset Not Avail, Rtnd to Cust DEFJ Deferred-Tools/Equip Not Avail, Rtnd to Cust DEFK Deferred-Mil Mission Pri, Rtnd To Cust DEFL Deferred-Cust Funds Not Avail DEFP Paint/Corrosion Control Required, Rtnd to Cust DEFS Body/Welding/Glass/Fabric Repairs Reqd, Rtnd to Cust
Mission Critical:
yes - the WO need to remain Open so they are reported on the USMC Deferred maintenance report until a decision is made to Fund or Dispose of the asset.
Benefits:
Allows visibility of Maintenance actions that need to be addressed for funding or disposal of asset.
Users:
Everyone |
|
Create MU Role for Custodian-RO-RI
|
01739
|
MU |
USMC |
New |
Description:
There is no M&U Role with the limited functions for the USMC Deferred Maintenance project
Recommended:
Create a Role named M&U - Custodian/RO/RI. This role must be able to create a WO, Update the WO, Create Warranties, create preventive maintenance plans.
Mission Critical:
Yes - the user community must have a limited role so they cannot perform more functions than necessary and it limits the impact on their workload for training.
Benefits:
Limits the amount of training the personnel must complete.
Users:
Everyone |
|
Create a M&U Dashboard entry for Deferred Maintenance
|
01738
|
PA |
USMC |
New |
Description:
Maintenance States and no display of the total cost of the WOs in Deferred States.
Recommended:
Create a entry in the M&U Dashboard that shows the Open Work Orders in any of the Deferred Maintenance States below. Add the data elements for Estimated Labor and Estimate Parts to the fields available on the data grid.
Mission Critical:
no - this data can be obtained in other methods but this does make the process more efficient.
Benefits:
Allows an efficient method to obtain the WOs that have been reported as Deferred for reporting to leadership
Users:
Everyone |
|
Auto Update of WO State Cd for Deferred Maintenance.
|
01737
|
PA |
USMC |
New |
Description:
There is no function in DPAS to automatically change the WO State Cd when a threshold is met for an Open WO to be deemed as Deferred Maintenance to meet the USMC policy.
Recommended:
Create a process that will udpate the WO State Cd to Deferred - No Funds Available. When the Doc # is blank and the WO has been open for longer than 120 days for CONUS and 150 days for OCONUS. May need to add a checkbox to the UIC record for the user to indicate which UICs are CONUS vs OCONUS.
Mission Critical:
Yes - the accurate updating of the WO to meet the Deferred Maintenance requirements for the USMC will enhance the ability to close the NFR received.
Benefits:
Eliminates the user losing track of WOs or not updating them accurately for the Deferred Maintenance requirements.
Users:
Everyone |
|
ASP.NET Session State
|
01736
|
PA |
Leidos |
New |
Description:
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.
Recommended:
Update the following environments to use the ASP.NET Session State with SQL Server In-Memory OLTP Database Session Provider
Mission Critical:
With the additional users being added to support Air Force Maintenance, this change is required
Benefits:
Reduced locking and latch contention resulting in better performance, stability and responsiveness.
Users:
Yes. All users could see an improvements with this change.
|
|
Automate Transfer of Phyical Inventory Data from Handheld to DPAS
|
01735
|
PA |
Leidos |
New |
Description:
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.
Recommended:
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.
Mission Critical:
highly desire and requested
Benefits:
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
Users:
all inventory personnel responsible for conducting/reporting physical inventory counts
|
|
SCR_01734 - Customer Support Request
|
01734
|
Enterprise |
Leidos |
New |
Description:
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.
Recommended:
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.
Mission Critical:
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.
Benefits:
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.
Users:
The capability will be provided to all DPAS users.
|
|
Submit Materiel Mgmt Accounting Transactions to Advana
|
01733
|
Enterprise |
USAF |
New |
Description:
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.
Recommended:
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.
Mission Critical:
Yes. With Advana having all financial feeder transactions, it should include those generated by DPAS's Materiel Management module.
Benefits:
Provides full accounting of all DPAS accounting activity. Enables a reconciliation of all accounting transactions between the source and financial system.
Users:
All customers requiring financial reporting for materiel/equipment held within the Materiel Management module. |
DPAS Support
Defense Property Accountability System
