|
Add My Queries to Grid Options for Inventory Activity Inquiry
|
01876
|
Warehouse |
NSWC: WARCOM |
New |
Change Request: Process Improvement
Description:
Lack of ability to tailor the Inventory Activity Inquiry data based on user preference.
Recommended:
Add "My Queries" in the Grid Options on the Inventory Activity Inquiry.
Mission Critical:
Allow the user to quickly retrieve the needed information based on their preference.
Benefits:
This improvement would improve time/cost on the user. This would eliminate the need to remove and add columns every day so they user can review the activity in their needed format.
Frequency: Daily
Users:
This problem affects all current users. |
|
Include Inspections for Issued Assets in WH Activity Report
|
01875
|
Warehouse |
NSWC: WARCOM |
New |
Change Request: Process Improvement
Description:
Adding completed Assessments of Issued out assets to the Warehouse Activity report.
Recommended:
Include assessments of issued out assets in the Warehouse Activity report.
Mission Critical:
The ideology of the Warehouse Activity report should be to include all completed actions to include actions completed on assets issued out as they still have the Owning DoDAAC of the warehouse.
Benefits:
This will improve accountability of assets for reporting purposes.
Frequency: Daily
Users:
This problem affects all current users.
|
|
Inspection Search Criteria Population
|
01874
|
Warehouse |
NSWC: WARCOM |
New |
Change Request: Process Improvement
Description:
Lock in the parameters within Inspection screen. Once you complete an inspection on selected inventory and go back to the available inventory, the filters set in place are reset. This requires you to input your filters/parameters after each inspection which greatly affects the time it takes to complete all the required inspections for that period.
Recommended:
Implement the same functionality to the inspection screen which is used on the Inventory Update screen. When updates are done on the selected inventory the available inventory does not remove previously set filters.
Mission Critical:
This functionality would greatly reduce the time it takes for users to complete their inspections by removing the need to repeatedly set their filters after each inspection.
Benefits:
Drastically reduces Time/Cost
Frequency: Daily
Users:
This problem affects all current users. |
|
Mass Assessment and Repair
|
01873
|
Warehouse |
NSWC: WARCOM |
New |
Change Request: Process Improvement
Description:
When completing assessments on hundreds of assets the lack of ability to assess multiple assets at once if they all receive the same type of repair.
Recommended:
Give the ability to select more than one asset at a time during the assessment process when completing a repair.
Mission Critical:
Without this, the smaller armories are still able to accurately complete their assessments but the larger armories have trouble doing so without being able to assign the same repair to multiple assets at once.
Benefits:
This improvement would reduce the time/cost of individuals as well as increase accountability since some armories currently forgo this process because of the time it takes completing assessments.
Frequency: Daily
Users:
This problem affects all current users. |
|
Upgrade Kendo and React Frameworks
|
01872
|
Enterprise |
Leidos |
New |
Change Request: Process Improvement
Description:
The DPAS applications utilize Kendo and React JavaScript frameworks that are in need of upgrading to the latest versions.
Recommended:
Upgrade the Kendo and React frameworks used by the DPAS application to the latest compatible and stable versions.
Mission Critical:
The upgrade of frameworks often introduces improvements to development capabilities which enable developers to deliver higher quality and more reliable software. It also prevents DPAS from operating on unsupported software that is a security violation.
Benefits:
The Kendo and React frameworks need to be regularly kept current to introduce new features, resolve bugs, and to eliminate any potential security vulnerabilities identified in the frameworks. These frameworks often come with improve development capabilities. These upgrades should add stability and reliability to the DPAS application.
Frequency: Hourly
Users:
These frameworks are continually evaluated and are used daily in most modules of the DPAS application. Approximate total users affected are 17K.
|
|
Improve DPAS login Process
|
01871
|
Enterprise |
Leidos |
New |
Change Request: Process Improvement
Description:
Currently the DPAS application relies on a Login process that is only compatible with non-modernized modules. This requires modernized modules to be launched after first navigating through existing non-modernized modules. This limits the ability for newer modernized modules to run standalone and can be frustrating for users wanting to bookmark the modern DAPS modules. Through the modernization of DPAS the number of non-modernized modules that can be used to launch these newer modules will continue to be reduced and eventually eliminated.
Recommended:
Improve the DPAS Login Process to remove the requirement of using a non-modernized modules to access newer modules and have the new modules initiate authentication themselves. To the extent possible, eliminate use of the non-modernized Login Process in favor of a single DPAS Login Process.
Mission Critical:
These changes will improve the user login and authentication process in DPAS for all DPAS modules.
Benefits:
The added run-ability of modernized DPAS modules will enhance the users' experience by allowing them to bookmark and authenticate directly to modernized DPAS modules. This will additionally help reduce development complexities when testing code changes as non-modernized applications will no longer be a requirement to a functioning test case.
Frequency: Daily
Users:
These changes will enhance the sign-on process for all 17K users.
|
|
Remove Unnecessary NSerivceBus Endpoints
|
01870
|
Enterprise |
Leidos |
New |
Change Request: Process Improvement
Description:
Two endpoints were setup for each of our modernized applications. In most cases it is only necessary to setup a single endpoint for each application. Our service agreement with NServiceBus indicates that we are billed for each endpoint. Having unnecessary endpoints increases the program's costs while not adding value to the program
Recommended:
Remove the extra, unneeded, endpoints in our API Layer and move the request tracking logic to the Service Layer of the DPAS modernized applications. This will reduce the overall number of endpoints consumed and reduce the associated costs.
Mission Critical:
Removing unnecessary endpoints will reduce costs and removing unnecessary code will improve maintenance and development speed.
Benefits:
Reducing the additional costs of endpoint usage.
Removing unnecessary code, reducing complexity, and saving future development time.
Frequency: -
Users:
The majority of our modernized applications will be affected. Approximate total users that use these systems are 17K.
|
|
Global Appsettings
|
01869
|
Enterprise |
Leidos |
New |
Change Request: Process Improvement
Description:
Currently DPAS stores enterprise settings by module. Enterprise settings should be the same throughout the system. By storing them by module it's time consuming to maintain when a change is required, and requires a reconciliation to determine which one is correct when they are not the same.
Recommended:
Create a global settings file that can be consumed into each module for settings that should remain constant across the enterprise.
Mission Critical:
This change will improve the reliability of the system and reduce the effort to maintain the system.
Benefits:
System settings such as logging configurations, API URLs, and other environment specific variables will remain uniform throughout the system.
Frequency: Hourly
Users:
This change will ensure reliability for all DPAS users. |
|
DLMS Modernization of Inbound 846
|
01868
|
Materiel Management |
Leidos |
New |
Change Request: Process Improvement
Description:
DPAS currently utilizes several methods to inbound and process DLMS transactions. These methods are commonly nested in close proximity to other DPAS processes, resulting in maintenance and enhancement efforts to be difficult and in some instances it adds more risk than there needs to be of breaking other processes when a change is introduced. To address these issues, DPAS is proposes to centralized the DLMS logic into a standalone service. This technical change will standardized the DLMS processing and logic with increased use of schema XSDs.
Recommended:
Design / develop a standalone DLMS Micro Service with a dedicated Database that interfaces with DPAS modules that utilize DLMS transactions. The initial DLMS Micro Service will support the inbounding of the DLMS 846D, 846P, 846R, and 846S. There will be future SCRs submitted to support additional DLMS transaction sets.
Mission Critical:
DPAS Tech Refresh - DLMS
Benefits:
Reduces the time/cost to implement DLMS changes. This change will increase throughput.
Frequency: Hourly
Users:
The DLMS 846* was flagged by DPAS Functionals for the initial fielding.
Inbound Volume, as of 1/1/2019: 184801 (846P), 497904 (846R), and 2 (846S)
|
|
DLMS Modernization of 846 Outbound
|
01867
|
Materiel Management |
Leidos |
New |
Change Request: Process Improvement
Description:
DPAS currently utilizes several methods to outbound DLMS transactions, these methods are commonly nested in close proximity to other DPAS processes. The objective of this DPAS Tech Refresh it to centralized DLMS processing and provide a standalone Micros Service for DLMS. This SCR is to implement the change to support the out bounding of the DLMS 846* transaction sets.
Recommended:
Usage of standalone DLMS Microservice, that interfaces with DPAS modules, and handles the outbounding of the 846P, 846R, 846S, and 846D. Iterative roll out and deprecation of legacy code.
Mission Critical:
DPAS Tech Refresh - DLMS
Benefits:
Reduces the Time/Cost for implementing DLMS changes and improves the overall processing efficiency for outbound DLMS traffic.
Frequency: Hourly
Users:
The 846 was flagged by DPAS Functionals for high volume of bugs.
Outbound Volume, as of 1/1/2019: 3 (846P) and 58,066 (846R)
|
|
Create job to run WCUSS47 [Active Assets and 60 Days Inactive Assets] in PA
|
01866
|
PA |
Leidos |
New |
Change Request: Process Improvement
Description:
DPAS has a custom extract that provides data to the Army monthly. It's a listing of active assets and the last 2 months of assets that have been dropped from DPAS . The DPAS PM runs the real-time report and provides the data to the Army. The DPAS PM is requesting that the data be sent to Advana, thus removing the DPAS PM from having to run the extract and deliver the information contained in the real-time report to the Army POC. The real-time report is WCUSS47 - Army Active Assets and last 2 Months of Inactive Assets.
Recommended:
Eliminates manual run and delivery of the data.
Mission Critical:
Improves efficiency
Does not require the DPAS PM to run and distribute the output / notify another person to run the job when they are out of the office.
Benefits:
Improves efficiency
Does not require the DPAS PM to run and distribute the output / notify another person to run the job when they are out of the office.
Frequency: Monthly
Users:
This is a business change in the delivery of the same data. POC is Mr. Joseph Stossel. |
|
Detail SKO ICN Report
|
01865
|
Warehouse |
Navy: NECC |
New |
Change Request: New System Process
Description:
The ICN report does not provide the minimum amount of data fields to provide our NECC system (RCRP) with enough data fields to calculate readiness as the system is currently structured.
Recommended:
NECC requests the ability to extract known data from the ICN report, which would require an expansion of the fields currently available. The ICN report as it exists today can dive into the contents of SKO kits indicating that that data is already in the DPAS system. NECC is requesting a report that would show kit component stock#, Stock serial#, SKO#, SKO serial # and SKO secondary serial #
Mission Critical:
N/A
Benefits:
Provides line item data for readiness reporting.
Frequency:
Monthly
Users:
Minimum users at ECH III command when running the ICN report. |
|
Add DoD Serial Number to WPMAR20R (report)
|
01864
|
MU |
USAF: AvSE |
New |
Change Request: Process Improvement
Description:
DoD/Secondary Serial Number is the AF most commonly used equipment identifier within a maintenance shop. Not having this identifier available on the report requires users to maintain a separate cross-reference sheet to convert DoD/Secondary Serial Number (not on the report) to asset Serial Number (on the report). The Air Force uses the DoD Serial Number field for the legacy system identifier to ensure linkage to history in the legacy systems. This number is also commonly stenciled or etched onto the equipment for easy visibility and identification.
Recommended:
Add DoD/Secondary Serial Number to the Upcoming Maintenance Schedule report (WPMAR20R).
Mission Critical:
AFI 21-101, Aircraft and Equipment Maintenance Management
Benefits:
More accurate maintenance documentation, quicker identification of equipment requiring inspection. Easier and quicker leadership briefings on upcoming maintenance (a policy requirement).
Frequency: Daily
Users:
~10K users affected
|
|
DLMS ASC 1428 (856S Transaction Type Code AZ)
|
01863
|
Enterprise |
Leidos |
New |
Change Request: Policy/ Regulatory
Description:
The DLMS Approved Standards Change (ASC) 1428 eliminates the use of the DLMS 856W and incorporates the functionality within the DLMS 856S Implementation Convention. DPAS requires a change to the generation of the DLMS 856S Shipment Status to support the turn in of Hazardous Materiel that is identified with in DLMS ASC 1428.
Recommended:
Add new Transaction Type Code to the DLMS 856S generation process: AZ (Disposal Shipment Advice) - Use to indicate this transaction provides Hazardous Material/Hazardous Waste shipment status information for turn-in of material to DLA Disposition Services. In addition to supporting the new Transaction Type Code, DPAS will need to incorporate the additional elements required for this transaction type within the DLMS 856S transaction.
Mission Critical:
Benefits:
Required for the submission / notification of a shipment of materiel to DLA Disposition Services.
Frequency: Daily
Users:
DPAS generates DLMS 856S from the following applications: Property Accountability, Warehouse Management and Materiel Management. No research has been conducted to determine how many user are turning in materiel that is classified as being Hazardous.
|
|
Add DLMS ADC 1422 to ICP
|
01862
|
Materiel Management |
AF: GFM-A |
Done |
Description:
DLMS ADC 1422 revises the DLMS 832N Catalog Data transaction and adds a new qualifier to identify the procurement instrument identifier (PIID) authorizing the contractor to perform work on behalf of the government.
Recommended:
With DPAS current support, the Air Force CICP programs are required to record the authorizing contract when transmitting materiel master records via the DLMS 832N. This qualifier mirrors the DLMS 947I, Inventory Adjustment Transaction to ensure consistency. Recommended Solution - update the DPAS processing logic to accept, store and update the PIID transmitted by the DLMS 832N transaction. In addition to updating the DPAS catalog, the processing logic should associate the new stock number to the AF CICP/GFM contract number.
Mission Critical:
Yes - This SCR requires implementation for inventory accountability and to accurately report the financial value of the inventory held by the contractor. This SCR is being submitted to implement DLMS ADC 1422.
Benefits:
The benefits of this SCR fix a material weakness resulting from inability to transmit and receive the authorizing contract via the DLMS 832N. The authorizing contract is a data element required by DoDI 500.64 section 4.6.
Users:
ALL AF GFM-A users of DPAS
Completed – Release 2023.1.6 – 24 March 2023 |
|
DPAS Health Monitor
|
01861
|
Enterprise |
Leidos |
In Progress |
Change Request: Process Improvement
Description:
Current detection and notification of problems in the DPAS system is handled by code within the applications and users that may report problems they encounter. We propose to augment these methods by adding an automated process that will routinely check the health of the applications in the DPAS system.
Recommended:
Create a health monitor that will regularly check the health of DPAS applications. A UI will also be made available in non-production environments to allow DPAS developers to view the health of monitored applications and details of health checks.
Mission Critical:
Health monitoring is generally accepted best practice for web applications. According to Microsoft: "If services cannot send some sort of "I'm alive" signal, either on demand or on a schedule, your application might face risks when you deploy updates, or it might just detect failures too late and not be able to stop cascading failures that can end up in major outages." See full article: https://learn.microsoft.com/en-us/dotnet/architecture/microservices/implement-resilient-applications/monitor-app-health
Benefits:
Improved reliability. The monitor will not be user facing, but it affects the DPAS modules the use by reducing the effects of slow-downs and service interruption.
Frequency: Hourly
Users:
The frequency of system health checks will be based upon the experience identified in its use. DPAS anticipates that if there if value that each service and web site may be checked every minute or couple of minutes depending on the check's efficiency and system performance. This tool is not a DPAS User Interface object. It's intended user base are DPAS Support personnel.
Partially Completed – Release 2023.1.4 – 24 February 2023 |
|
DPAS to NAVAIR Data Interface
|
01860
|
Enterprise |
Navy: NAVAIR |
New |
Change Request: Process Improvement
Description:
Currently NAVAIR (Command Property Office) receives a monthly file from DPAS and manually processes the data
Recommended:
We would like to either set up a direct data feed to DPAS where we can pull a weekly table of the requested data fields or set up a weekly file drop of the requested fields to our server so we can use our extraction tool to import the data into our data warehouse.
Mission Critical:
Our goal is to automate this data transfer for the Command Property Office at NAVAIR to minimize man hours and increase efficiency.
Benefits:
This will minimize man hours spent processing these files and improves accuracy when analyzing the data for the end user. The DPAS data is being used for monthly inventory scorecards. The value of inventory is being visualized in Qlik for monthly and yearly trend and is also used for POG Billings to PMAs by the CPO. It will also be used for our warehouse consolidation effort and COOPER storage locations updates.
Frequency: Weekly
Users:
20+ users but we hope for that to grow once the way we process this data becomes easier. |
|
Maintenance Schedule/Work Plan System Update
|
01859
|
MU |
AF: AvSE |
In Progress |
Change Request: Process Improvement
Description:
Problem: When Work Orders are closed that are comprised of Work Plans that are shared across multiple Maintenance Schedules, DPAS does not know which Maintenance Schedule to update and therefore updates all. This in turn, will cause DPAS to not generate Work Orders on required inspections and reflect inspections as being accomplished that have not been accomplished. This is a critical safety issue.
Recommended:
Create a switch or drop down menu at the Program (Maintenance Director) level to ensure only the maintenance schedule associated with a work order is updated when the work order is closed.
Mission Critical:
None Provided
Benefits:
With the ability to only update Maintenance Schedules whose Work Orders that were generated from that Maintenance Schedule are completed, It ensures inspection integrity. This will also eliminate the issue users are having with duplicate Work Orders or Work Orders not generating at all. Finally, this will eliminate the major safety implication that are currently present.
Frequency: Daily
Users:
Thousands of times a day across the enterprise.
Partially Completed – Release 2023.1.4 – 24 February 2023
Partially Completed – Release 2023.1.6 – 24 March 2023
|
|
Expand MU User Preferences
|
01858
|
MU |
AF: VSCOS |
New |
Description:
DPAS work order processing can involve entering repetitive information across multiple sections or sub work orders. User can experience selecting the same option multiple times when adding, updating or closing a work order. Having to repeat the process adds task time and increases processing errors.
Recommended:
Expand default options under User Preferences:
1. Add preference search criteria for work plan browse within work order; use radio button for Other Activity Plans. When selected the My Plans toggle will default to off (grayed out) when the user preforms a work plan browse to add or update work orders.
2. Add preference for default Work Order State Code when adding a sub work order. User would select a preference from drop-down menu listing available Work Order State Code options. When the preference is set, the Work Order State Code pre-populates when adding a new sub work order. User can then change the Work Order State Code as needed if default does not apply to specific work order.
3. Add preference for default Work Order State Code when closing a work order. User would select a preference from drop-down menu listing available Work Order State Code options. When the preference is set, all Work Order State Codes will default to the user preference when the Work Order Status Code is changed to C – Closed. User can then change the Work Order State Code as needed if default does not apply to specific work order.
Mission Critical:
Accurate work order processing is critical to data integrity and reporting to FAST, DRRS and other systems.
Benefits:
This change will reduce task time, need for work order processing as well as increase data accuracy by reducing repetitive entry.
Users:
This improvement will benefit the Department of the Air Force and all other DoD Agency's |
|
Create Deferred Parts option with Open Maint Issue
|
01857
|
MU |
AF: VSCOS |
New |
Description:
Department of the Air Force (DAF) vehicle enterprise's maintenance activities have a need to delay a sub-work order task and/or defer parts, but require the warehouse maintenance issue to remain open. Although the part is deferred, the maintenance issue still must process and hold part(s) for future use (e.g., installation of vehicle). Currently, the system will move the maintenance issue to DE-Deferred status when deferring the sub-work order. This effectively cancels the maintenance issue as no further action is possible within DE-Deferred status. This action eliminates the demand signal within the system and requires the maintenance technician to externally communicate with the warehouse to ensure the requisition is fulfilled for future use.
Recommended:
Create an option to cancel a work order requisition and defer the part(s) with an open maintenance issue. When selecting this option the maintenance issue links to the work order, updates to DE-Deferred and creates a new maintenance issue linking to the asset id. New maintenance issues unlinked to a work order would indicate the need to complete the pick process or create a backorder for installation after receipt.
Mission Critical:
This is critical to ensure fleet readiness by eliminating supply chain disruptions. Delaying fulfillment of a maintenance issue compounds long lead times within part acquisition.
Benefits:
This change will reduce task time, need for work order processing as well as increase data accuracy by reducing repetitive entry.
Users:
This improvement will benefit the DAF and all other DoD Agency's |
DPAS Support
Defense Property Accountability System