|
01694 |
DPAS GEX Data Feed |
Enterprise |
USSOCOM |
Done |
Description 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.
Recommended 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.
Mission Critical 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.
Benefits 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.
Users All. Allows for visual reporting at all levels.
Partially Completed – Release 2022.3 – 04 November 2022
Partially Completed – Release 2023.3.3 – 11 August 2023
Partially Completed – Release 2024.3.2 – 26 July 2024 |
|
|
01693 |
Conversion spreadsheet load by users for Multiple AUIC/UIC |
Enterprise |
AF: SPT EQUIP |
New |
Description 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.
Recommended Provide a capability for users to be able to upload conversion spreadsheets for validation and upload.
Mission Critical
Benefits Reduces workload for DPAS contract support and time that users waits until file is finally uploaded.
Users ALL |
|
|
01692 |
UIC applied priority table |
FSM |
AF: SPT EQUIP |
New |
Description 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.
Recommended Create a reference table that identifies where the on-hand balance should be applied as the UIC prioritization table outlines
Mission Critical
Benefits
Users |
|
|
01691 |
DRRS report file |
Enterprise |
AF: SPT EQUIP |
Done |
Description The Air Force needs a file to report the unit readiness status to DRRS based on the data in PA and FSM.
Recommended: 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
Mission Critical Services are mandated to report DRRS readiness capabilities IAW CJCSI 3401.02B
Benefits Improves accuracy and accountability for DRRS readiness reporting
Users Yes
Completed – Release 2022.3 – 04 November 2022 |
|
|
01690 |
Supervisory Master Data manager role |
Enterprise |
AF: SPT EQUIP |
Done |
Description 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.
Recommended 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.
Mission Critical 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.
Benefits Improves accountability
Users
Completed - Release 2024.1.6 |
|
|
01689 |
Registry Recon Status in PA |
Enterprise |
AF: SPT EQUIP |
New |
Description 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.
Recommended 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.
Mission Critical The equipment managers in the AF deem it as mission critical, as they need this information to sufficiently manage SA/LW on equipment accounts.
Benefits Improves accountability.
Users All users |
|
|
01688 |
FAD Validation ILS-S Interface |
Enterprise |
AF: SPT EQUIP |
New |
Description The Master Data Manager profile allows users with access to manually load, update and delete a AUIC/UIC
Recommended 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.
Mission Critical 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.
Benefits Improves accountability, accuracy and oversight.
Users All users |
|
|
01687 |
Receive/Accept Multiple Items |
Enterprise |
AF: VSCOS |
New |
Description 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.
Recommended 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.
Mission Critical 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.
Benefits 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.
Users This change will improve part processing operations for all 8,000 Air Force Vehicle Management community warehouse users. |
|
|
01686 |
Substitute Stock Number |
Enterprise |
AF: VSCOS |
New |
Description The Substitute Stock Number feature does not work across all the functions of the Warehouse module.
- Maintenance Issue requests for obsolete items requires cancellation and resubmission.
- Cannot replace SKO Components with compatible items and changing the SKO catalog affects all other kits sharing same configuration.
Recommended 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.
Mission Critical 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.
Benefits Improves data accuracy and tool/part accountability while streamlining procedures.
Users This change will streamline Maintenance Issue and SKO management procedures for all Air Force vehicle management Warehouse users |
|
|
01685 |
Return Items from M&U to WH |
Enterprise |
AF: VSCOS |
New |
Description 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.
Recommended 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.
Mission Critical 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).
Benefits Solution will increase accuracy of inventory items and enable proper accountability of sustainment funds.
Users This change will improve part management for all Air Force vehicle management users performing Maintenance Issues between Warehouse and Maintenance and Utilization modules. |
|