Data Aggregation and Visualization RFI PWS.pdf

PERFORMANCE WORK STATEMENT

For AI-Powered Data Aggregation and Visualization Tool for Minuteman III

Prepared For:

Air Force Nuclear Weapons Center (AFNWC/NIM) Hill Air Force Base, Utah

Date: [Current Date]

TABLE OF CONTENTS

SECTION I: DESCRIPTION OF SERVICES

1.0 BACKGROUND

2.0 SCOPE

3.0 TASKS/REQUIREMENTS

4.0 PROGRAM MANAGEMENT

5.0 SECURITY REQUIREMENTS

6.0 DELIVERABLES

SECTION II: SERVICE SUMMARY

SECTION III: GOVERNMENT-FURNISHED INFORMATION

SECTION I: DESCRIPTION OF SERVICES

1.0 BACKGROUND

The Minuteman III (MMIII) Systems Directorate currently manages critical data across approximately 60 disparate and disconnected systems, including databases, local hard drives, and shared networks. This fragmented data environment necessitates significant manual labor to compile information, assess weapon system risks (both for parts attrition and functional age-out), and maintain overall situational awareness. Past efforts to establish a unified Product Lifecycle Management (PLM) digital ecosystem have not come to fruition due to a range of challenges. While separate tools, including AIMM3 (Analytics Intelligence for MMIII), are successfully used for fleet health metrics, critical gaps remain in centralized data access, querying, and visualization. This Performance Work Statement (PWS) establishes the requirement for a contractor to develop an Artificial Intelligence (AI) tool to address these specific gaps.

2.0 SCOPE

The contractor shall design, develop, test, and implement an AI-powered software tool to provide a centralized data query and assessment capability for the MMIII program. The primary objective is to bridge the existing gaps in data accessibility and technical data assessment. The tool shall provide a single, unified interface for users to query and retrieve information from the various MMIII data sources without needing to access each source system individually. It shall provide enhanced query capability based on user-defined questions. It shall also provide enhanced visualization capabilities for technical files such as 2D/3D drawings and functional diagrams. This effort will complement, not replace, the existing AIMM3 metrics tool.

3.0 TASKS/REQUIREMENTS

The contractor shall perform the tasks detailed below:

3.1 Centralized Data Querying

The contractor shall develop a feature that provides a unified search and retrieval capability.

• 3.1.1 The system shall be able to connect to and pull data from the various MMIII data sources as specified in the Government-Furnished Information (GFI). These sources include, but are not limited to: MMIII Health of the Fleet metrics, drawings, specifications, interface control documents, MMIII supply data, MMIII maintenance data, and the JIRA Weapon System Risk Repository.

• 3.1.2 The tool shall provide a single user interface for querying the connected data sources. It shall not serve as the Authoritative Source of Truth (ASOT) but must have the ability to pull data from the respective ASOTs in near real-time.

3.2 Enhanced Data Visualization

The contractor shall develop a feature to query, access, and visualize complex technical data.

• 3.2.1 The system shall provide an intuitive way to navigate and view technical data, including 2D drawings, 3D models, functional flow diagrams, and other figures.

• 3.2.2 This capability should be designed to improve the ease of training for new personnel and aid in the navigation of complex system architectures.

3.3 System Performance and Risk Mitigation

• 3.3.1 Performance: The tool shall be designed for efficiency, aiming to reduce the time and manual effort currently required for data compilation tasks by a measurable amount, to be defined and agreed upon during the first Program Management Review (PMR).

• 3.3.2 Risk Mitigation: The contractor shall implement safeguards and continuous validation checks to ensure the accuracy and integrity of the data presented by the tool. The system must accurately reflect the data from the source systems.

4.0 PROGRAM MANAGEMENT

• 4.1 Project Management Plan: The contractor shall deliver a comprehensive Project Management Plan within 30 days of contract award. This plan will outline the contractor's approach to managing the project, including timelines, milestones, and a software development lifecycle methodology.

• 4.2 Program Management Reviews (PMRs): The contractor shall conduct quarterly PMRs with government stakeholders. These reviews will cover project status, progress against milestones, risks, and a demonstration of completed work.

• 4.3 Reporting: The contractor shall provide Monthly Status Reports detailing activities completed, upcoming work, and any issues or risks encountered.

5.0 SECURITY REQUIREMENTS

• 5.1 Data Handling: The contractor shall handle all data in accordance with DoD regulations. The initial phase of the project will involve accessibility for Controlled Unclassified Information (CUI) at Impact Level 5 (IL5). Future efforts may include work with Secret data at Impact Level 6 (IL6).

• 5.2 Personnel: Contractor personnel requiring access to government systems or data will be required to have the appropriate security clearances as specified by the government.

6.0 DELIVERABLES

The contractor shall provide the following deliverables to the Government in accordance with the specified schedule:

Deliverable Description Due Date

Project Management Plan Comprehensive plan outlining approach, timelines, and methodology.

30 days after contract award

Monthly Status Reports Details of activities completed, upcoming work, risks, and issues.

5th business day of each month

PMR Briefing Materials Slide deck and demonstration materials for Quarterly PMRs.

5 business days prior to each PMR

AI Tool Software Release Fully functional AI tool executable, including source code and configuration files.

As defined in the approved Project Management Plan

Technical Documentation & User Manuals

System architecture diagrams, administrator guides, and end-user training materials.

Prior to final Government Acceptance

SECTION II: SERVICE SUMMARY

The government will monitor contractor performance against the standards listed in the table below.

Performance Objective

PWS

Paragraph

Performance Threshold Method of Surveillance

Centralized Data Querying

3.1 The tool successfully connects to and

queries at least 95% of the initial set of specified data sources. Search results are returned with 99% accuracy against source data.

Quarterly PMR demonstrations and Government acceptance testing.

Enhanced Data Visualization

3.2 The tool can render and display specified

technical file types (e.g., 2D/3D drawings) with no errors. User feedback from government stakeholders indicates the interface is intuitive.

Quarterly PMR demonstrations and user feedback surveys.

Program Management & Reporting

4.0, 6.0 All reports and deliverables are submitted on time. No more than one late submission per quarter. PMRs are held as scheduled.

COR review of deliverable submissions.

Security Compliance

5.0 100% compliance with specified data handling and security requirements. No security incidents or data spillage.

Periodic security audits and reviews.

SECTION III: GOVERNMENT-FURNISHED INFORMATION

The Government will provide the following information and access:

• A detailed list of the ~60 data sources and guidance on how to access them.

• Access to key stakeholders, including MMIII Engineering, Maintenance, and Supply personnel, for requirements clarification and feedback sessions.

• Access to example data sets and technical files (drawings, models, etc.) required for development and testing.

• Required Air Force Data Sources shall comprehensively include, but are not limited to, the following:

# Air Force Data Source:

1 MMIII Health of the Fleet Metrics 2 Drawings 3 Specifications 4 Interface Control Documents 5 Hardware Data Manuals 6 Technical Orders 7 Configuration Item Identifiers 8 Functional Models of the Weapon System Architecture Model 9 D043 Supply Data (stock numbers, part numbers, ES codes, etc.)

10 Supply Status (# of assets and condition status in D200A, SBSS, CAS) 11 Supply Requirements Forecast (D200A) 12 Work Unit Code Library 13 Work Breakdown Structure Metadata (attrition risk, age-out risk, handling strategy) 14 JIRA Weapon System Risk Repository

15 107 (ETAR) Library/History 16 202 Library/History 17 PADS data from the field 18 IMDS maintenance data 19 Field Watchlist Status (P2/P3 status) 20 Maintenance logs from the depot 21 Test Plans/Test Reports 22 Class I Baseline Change Systems Engineering Database 23 Program Management Reviews 24 Health of the Fleet Reviews 25 Workflows 26 AFGSC Director Update Briefs 27 MMIII Handbooks 28 AFNWC Instructions 29 AFGSC Instructions 30 AFMC Instructions 31 AF Instructions