1.0 Introduction and Purpose
The Department of the Air Force (DAF) is conducting market research to identify parties with the requisite capabilities, resources, and experience to provide comprehensive product support and sustainment integration for the Air Base Air Defense for Missile Defense (ABAD MD) System.
This RFI is issued solely for information and planning purposes and does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This request for information does not commit the Government to contract for any supply or service whatsoever.
2.0 Background and Operational Posture
The ABAD MD system is a critical, actively deployed capability for air base defense. The program is executing Phase 5, which focuses on the sustainment of currently fielded systems operating in active defense postures. Leveraging Tactical Operations Center Light (TOC-L) hardware, these Command and Control (C2) systems are deployed in support of immediate warfighter operations.
Historically, this system has relied on proprietary Original Equipment Manufacturer (OEM) software. The Government's objective for the next phase of this program is twofold:
- Maintain strict, uninterrupted operational readiness and cybersecurity posture for the actively fielded legacy baseline.
- Execute a deliberate, phased modernization effort to replace proprietary components with open-standard, non-proprietary software, eliminating vendor lock without degrading current capabilities.
3.0 Scope of Work and Phased Approach
The contractor shall be responsible for activities ensuring successful continuous sustainment and modernization of the ABAD MD system. The Government anticipates the following:
- Core Sustainment Operations: Full assumption of ABAD MD and TOC-L Product Support Hubs, Tier I-III help desk operations, provision of cleared Field Service Representatives (FSRs) to active sites, and routine cybersecurity patching/Information Assurance Vulnerability Alerts (IAVAs).
4.0 System Constraints and Available GFI/GFP
The ABAD MD system's current operational baseline relies on integrated software components proprietary to Lockheed Martin. The Government does not possess source code for these specific components:
- UCI Blaster: Universal Command and Control Interface (UCI) formatting/routing software.
- PIPES: UCI Message translation utility.
- UCI Blaster Manager: Management interface for UCI routing.
- NKE Emulator: System emulation capability.
- Screen Watchdog / BIF Hub: System monitoring and screen recording functionalities.
4.1 Available Government Furnished Information/Property (GFI/GFP):
To facilitate a competitive transition and support the OSA migration, the Government intends to provide the awardee with:
- System Interface Control Documents (ICDs) defining the inputs/outputs of the proprietary components listed above.
- Full access to ABAD MD TOC-L hardware baselines and software test-beds (SIL/ITF).
- The existing Risk Management Framework (RMF) package and system architecture diagrams.
5.0 Operational Metrics and Scale
To assist industry in formulating realistic responses and transition plans, the following program metrics are provided for context:
- Multiple Fielded Systems: (PLANNING NUMBERS ESTIMATED)
15 units deployed across CONUS (account for one across country) OCONUS (PACAF & USAFE)
- Support Hubs:
- Two (1) Regional Support Hubs requiring 24/7/365 coverage.
- Ticket Resolution Time: Average trouble ticket resolutions from highest to lowest response: 10 Level I/ 20 Level II/ 40 Level III sustainment tickets per month, degraded to interoperable full-mission status
- Cybersecurity: Contractor shall support patching cadence from LOW through EMERGENCY vulnerability severity
1.0 Introduction and Purpose
The Department of the Air Force (DAF) is conducting market research to identify parties with the requisite capabilities, resources, and experience to provide comprehensive product support and sustainment integration for the Air Base Air Defense for Missile Defense (ABAD MD) System.
This RFI is issued solely for information and planning purposes and does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This request for information does not commit the Government to contract for any supply or service whatsoever.
2.0 Background and Operational Posture
The ABAD MD system is a critical, actively deployed capability for air base defense. The program is executing Phase 5, which focuses on the sustainment of currently fielded systems operating in active defense postures. Leveraging Tactical Operations Center Light (TOC-L) hardware, these Command and Control (C2) systems are deployed in support of immediate warfighter operations.
Historically, this system has relied on proprietary Original Equipment Manufacturer (OEM) software. The Government's objective for the next phase of this program is twofold:
- Maintain strict, uninterrupted operational readiness and cybersecurity posture for the actively fielded legacy baseline.
- Execute a deliberate, phased modernization effort to replace proprietary components with open-standard, non-proprietary software, eliminating vendor lock without degrading current capabilities.
3.0 Scope of Work and Phased Approach
The contractor shall be responsible for activities ensuring successful continuous sustainment and modernization of the ABAD MD system. The Government anticipates the following:
- Core Sustainment Operations: Full assumption of ABAD MD and TOC-L Product Support Hubs, Tier I-III help desk operations, provision of cleared Field Service Representatives (FSRs) to active sites, and routine cybersecurity patching/Information Assurance Vulnerability Alerts (IAVAs).
4.0 System Constraints and Available GFI/GFP
The ABAD MD system's current operational baseline relies on integrated software components proprietary to Lockheed Martin. The Government does not possess source code for these specific components:
- UCI Blaster: Universal Command and Control Interface (UCI) formatting/routing software.
- PIPES: UCI Message translation utility.
- UCI Blaster Manager: Management interface for UCI routing.
- NKE Emulator: System emulation capability.
- Screen Watchdog / BIF Hub: System monitoring and screen recording functionalities.
4.1 Available Government Furnished Information/Property (GFI/GFP):
To facilitate a competitive transition and support the OSA migration, the Government intends to provide the awardee with:
- System Interface Control Documents (ICDs) defining the inputs/outputs of the proprietary components listed above.
- Full access to ABAD MD TOC-L hardware baselines and software test-beds (SIL/ITF).
- The existing Risk Management Framework (RMF) package and system architecture diagrams.
5.0 Operational Metrics and Scale
To assist industry in formulating realistic responses and transition plans, the following program metrics are provided for context:
- Multiple Fielded Systems: (PLANNING NUMBERS ESTIMATED)
15 units deployed across CONUS (account for one across country) OCONUS (PACAF & USAFE)
- Support Hubs:
- Two (1) Regional Support Hubs requiring 24/7/365 coverage.
- Ticket Resolution Time: Average trouble ticket resolutions from highest to lowest response: 10 Level I/ 20 Level II/ 40 Level III sustainment tickets per month, degraded to interoperable full-mission status
- Cybersecurity: Contractor shall support patching cadence from LOW through EMERGENCY vulnerability severity
6.0 Information Requested from Interested Parties (Capabilities Statement)
To assess industry capability to execute a secure transition, sustain the legacy baseline, and engineer an open-architecture future, interested parties must provide a capabilities statement that directly addresses the following areas:
Evaluation Area
Requested Vendor Response & Strategy Details
1. Open Systems Architecture (OSA) Migration Plan
Modernization Strategy: Provide a technical concept for replacing the proprietary components listed in Section 4.0 (e.g., UCI Blaster, PIPES) with open-standard, non-proprietary software over a 12-to-24-month period.
UCI Integration:
Describe your firm's specific experience integrating and translating Universal Command and Control Interface (UCI) messages across disparate C2 sensors and effectors.
2. Risk Management Framework (RMF) & Cyber Security
Continuous ATO: Describe your approach to achieving and maintaining an Authority to Operate (ATO) for newly developed open-architecture components without disrupting the operational ATO of the actively deployed legacy baseline.
Patch Management: How will your firm manage Information Assurance Vulnerability Alerts (IAVAs) and routine patching during the transition phase before fully replacing the proprietary software?
3. Government Furnished Information (GFI) Needs
Required Government Support: Based on the GFI listed in Section 4.1, explicitly list any additional GFI, Application Programming Interfaces (APIs), or technical data your firm would require from the Government to successfully execute your proposed transition and migration plans.
4. Global Field Support & Help Desk Operations
Sustainment Operations: Summarize your corporate experience operating 24/7/365 Product Support Hubs and dispatching Field Service Representatives (FSRs) for complex, actively fielded Command and Control (C2) systems. Incumbent Capture: Briefly describe your strategy for recruiting, clearing, and transitioning incumbent personnel to maintain continuity of tactical knowledge.
5. Clearances & Personnel Qualification
Workforce Readiness: Verify your firm's ability to staff and maintain personnel with Top Secret/Sensitive Compartmented Information (TS/SCI) clearances, Special Access Program (SAP) eligibility, and DoD 8140.03 (DCWF) compliant cybersecurity certifications within the transition window.
Evaluation Area Box
Requested Vendor Response & Strategy Details
-Open Systems Architecture (OSA) Migration Plan
Modernization Strategy: Provide a technical concept for replacing the proprietary components listed in Section 4.0 (e.g., UCI Blaster, PIPES) with open-standard, non-proprietary software over a 12-to-24-month period.
UCI Integration:
Describe your firm's specific experience integrating and translating Universal Command and Control Interface (UCI) messages across disparate C2 sensors and effectors.
-Risk Management Framework (RMF) & Cyber Security
Continuous ATO: Describe your approach to achieving and maintaining an Authority to Operate (ATO) for newly developed open-architecture components without disrupting the operational ATO of the actively deployed legacy baseline.
Patch Management: How will your firm manage Information Assurance Vulnerability Alerts (IAVAs) and routine patching during the transition phase before fully replacing the proprietary software?
Government Furnished Information (GFI) Needs
Required Government Support: Based on the GFI listed in Section 4.1, explicitly list any additional GFI, Application Programming Interfaces (APIs), or technical data your firm would require from the Government to successfully execute your proposed transition and migration plans.
Global Field Support & Help Desk Operations
Sustainment Operations: Summarize your corporate experience operating 24/7/365 Product Support Hubs and dispatching Field Service Representatives (FSRs) for complex, actively fielded Command and Control (C2) systems. Incumbent Capture: Briefly describe your strategy for recruiting, clearing, and transitioning incumbent personnel to maintain continuity of tactical knowledge.
Clearances & Personnel Qualification
Workforce Readiness: Verify your firm's ability to staff and maintain personnel with Top Secret/Sensitive Compartmented Information (TS/SCI) clearances, Special Access Program (SAP) eligibility, and DoD 8140.03 (DCWF) compliant cybersecurity certifications within the transition window.
6.0 Information Requested from Interested Parties (Capabilities Statement)
To assess industry capability to execute a secure transition, sustain the legacy baseline, and engineer an open-architecture future, interested parties must provide a capabilities statement that directly addresses the following areas:
Evaluation Area
Requested Vendor Response & Strategy Details
1. Open Systems Architecture (OSA) Migration Plan
Modernization Strategy: Provide a technical concept for replacing the proprietary components listed in Section 4.0 (e.g., UCI Blaster, PIPES) with open-standard, non-proprietary software over a 12-to-24-month period.
UCI Integration:
Describe your firm's specific experience integrating and translating Universal Command and Control Interface (UCI) messages across disparate C2 sensors and effectors.
2. Risk Management Framework (RMF) & Cyber Security
Continuous ATO: Describe your approach to achieving and maintaining an Authority to Operate (ATO) for newly developed open-architecture components without disrupting the operational ATO of the actively deployed legacy baseline.
Patch Management: How will your firm manage Information Assurance Vulnerability Alerts (IAVAs) and routine patching during the transition phase before fully replacing the proprietary software?
3. Government Furnished Information (GFI) Needs
Required Government Support: Based on the GFI listed in Section 4.1, explicitly list any additional GFI, Application Programming Interfaces (APIs), or technical data your firm would require from the Government to successfully execute your proposed transition and migration plans.
4. Global Field Support & Help Desk Operations
Sustainment Operations: Summarize your corporate experience operating 24/7/365 Product Support Hubs and dispatching Field Service Representatives (FSRs) for complex, actively fielded Command and Control (C2) systems. Incumbent Capture: Briefly describe your strategy for recruiting, clearing, and transitioning incumbent personnel to maintain continuity of tactical knowledge.
5. Clearances & Personnel Qualification
Workforce Readiness: Verify your firm's ability to staff and maintain personnel with Top Secret/Sensitive Compartmented Information (TS/SCI) clearances, Special Access Program (SAP) eligibility, and DoD 8140.03 (DCWF) compliant cybersecurity certifications within the transition window.
7.0 Submission Instructions
Respondents are advised that all submissions become Government property and will not be returned. If a respondent submits proprietary, business-sensitive, or otherwise confidential trade secret information, it must be clearly and distinctly marked on a page-by-page basis. The Government will take reasonable precautions to safeguard properly marked proprietary data in accordance with applicable acquisition regulations. However, the Government assumes no liability for the loss, mishandling, or unauthorized disclosure of any proprietary information or materials that are not explicitly and properly marked, or that are submitted voluntarily in response to this notice. Respondents are solely responsible for adequately marking and protecting their intellectual property prior to submission.
