{"canonical":"https://abierto.us/opportunities/fa8612","key":"FA8612","url":"https://abierto.us/opportunities/fa8612","title":"Ground-Based, Medium-Caliber Gun Weapon System","solicitation_number":"FA8612_","notice_type":"r","open":true,"response_deadline":"2026-10-09T21:00:00Z","first_posted":"2026-06-26","last_posted":"2026-09-03","department":"DEPT OF DEFENSE","subagency":"DEPT OF THE AIR FORCE","office":"FA8612 AFLCMC C3BM C3","naics":null,"psc":null,"set_aside":null,"place_state":"OH","winner":null,"award_amount":null,"publications":[{"notice_id":"79774fcfc5794124923e3f497eba3846","title":"Request for Information (RFI) / Sources Sought Notice Product Support and Sustainment Integration for Air Base Air Defense for Missile Defense (ABAD MD) System","solicitation_number":"FA8612","notice_type":"r","base_type":"r","posted":"2026-06-26","posted_at":null,"due_at":"2026-07-06T19:00:00Z","due_date":"2026-07-06","cancelled":null,"archived":null,"archive_date":"2026-07-21","award_number":null,"awardee_name":null,"amount":null,"link_sam":"https://sam.gov/workspace/contract/opp/79774fcfc5794124923e3f497eba3846/view","enriched":false,"history":[]},{"notice_id":"fb5964a8810b47868b21ef3ec4f79e28","title":"Request for Information (RFI) / Sources Sought Notice Product Support and Sustainment Integration for Air Base Air Defense for Missile Defense (ABAD MD) System","solicitation_number":"FA8612","notice_type":"r","base_type":"r","posted":"2026-06-30","posted_at":null,"due_at":"2026-07-09T19:00:00Z","due_date":"2026-07-09","cancelled":null,"archived":null,"archive_date":"2026-07-24","award_number":null,"awardee_name":null,"amount":null,"link_sam":"https://sam.gov/workspace/contract/opp/fb5964a8810b47868b21ef3ec4f79e28/view","enriched":false,"history":[]},{"notice_id":"9e23698488284056940cda4a0de11d1c","title":"Ground-Based, Medium-Caliber Gun Weapon System","solicitation_number":"FA8612_","notice_type":"r","base_type":"r","posted":"2026-09-03","posted_at":null,"due_at":"2026-10-09T21:00:00Z","due_date":"2026-10-09","cancelled":null,"archived":null,"archive_date":"2026-10-09","award_number":null,"awardee_name":null,"amount":null,"link_sam":"https://sam.gov/workspace/contract/opp/9e23698488284056940cda4a0de11d1c/view","enriched":false,"history":[]}],"latest_notice_id":"9e23698488284056940cda4a0de11d1c","first_type":"r","notices":[{"dates":{"posted":"2026-06-26","response_deadline":{"raw":"2026-07-06T15:00:00-04:00","utc":"2026-07-06T19:00:00Z","date":"2026-07-06","time":"15:00:00","utc_offset_seconds":-14400}},"links":{"sam":"https://sam.gov/workspace/contract/opp/79774fcfc5794124923e3f497eba3846/view"},"naics":{},"title":"Request for Information (RFI) / Sources Sought Notice Product Support and Sustainment Integration for Air Base Air Defense for Missile Defense (ABAD MD) System","agency":{"office":{"code":"FA8612","name":"FA8612 AFLCMC C3BM C3"},"subtier":{"code":"5700","name":"DEPT OF THE AIR FORCE"},"department":{"code":"057","name":"DEPT OF DEFENSE"},"office_address":{"zip":"45434-7104","city":"DAYTON","state":"OH","country":"USA"},"organization_type":"OFFICE"},"status":{"active":false,"archive_date":"2026-07-21","archive_type":"auto15"},"contacts":[{"name":"Christine Basham","role":"primary","email":"christine.basham.1@us.af.mil"},{"name":"Veronica Schoultz","role":"secondary","email":"veronica.schoultz@us.af.mil"}],"base_type":{"code":"r","label":"Sources Sought"},"notice_id":"79774fcfc5794124923e3f497eba3846","provenance":{"extract":{"url":"https://s3.amazonaws.com/falextracts/Contract%20Opportunities/Archived%20Data/FY2026_archived_opportunities.csv","etag":"\"d9374b90a938e9923d910594731b7b57-106\"","fetched_at":"2026-09-16T00:55:27.040971Z","row_sha256":"f188e9a74ffaf72224656a4468db6d09736f4489488bc4404009d4f01656c9d8","last_modified":"2026-09-13T14:50:39Z"},"updated_at":"2026-09-16T00:55:27.040971Z","first_seen_at":"2026-09-16T00:55:27.040971Z"},"description":{"text":"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.","origin":"extract"},"notice_type":{"code":"r","label":"Sources Sought"},"schema_version":1,"solicitation_number":"FA8612","place_of_performance":{"zip":"45433","city":{"name":"Dayton"},"state":{"code":"OH"},"country":{"code":"USA"}}},{"dates":{"posted":"2026-06-30","response_deadline":{"raw":"2026-07-09T15:00:00-04:00","utc":"2026-07-09T19:00:00Z","date":"2026-07-09","time":"15:00:00","utc_offset_seconds":-14400}},"links":{"sam":"https://sam.gov/workspace/contract/opp/fb5964a8810b47868b21ef3ec4f79e28/view"},"naics":{},"title":"Request for Information (RFI) / Sources Sought Notice Product Support and Sustainment Integration for Air Base Air Defense for Missile Defense (ABAD MD) System","agency":{"office":{"code":"FA8612","name":"FA8612 AFLCMC C3BM C3"},"subtier":{"code":"5700","name":"DEPT OF THE AIR FORCE"},"department":{"code":"057","name":"DEPT OF DEFENSE"},"office_address":{"zip":"45434-7104","city":"DAYTON","state":"OH","country":"USA"},"organization_type":"OFFICE"},"status":{"active":false,"archive_date":"2026-07-24","archive_type":"auto15"},"contacts":[{"name":"Christine Basham","role":"primary","email":"christine.basham.1@us.af.mil"},{"name":"Veronica Schoultz","role":"secondary","email":"veronica.schoultz@us.af.mil"}],"base_type":{"code":"r","label":"Sources Sought"},"notice_id":"fb5964a8810b47868b21ef3ec4f79e28","provenance":{"extract":{"url":"https://s3.amazonaws.com/falextracts/Contract%20Opportunities/Archived%20Data/FY2026_archived_opportunities.csv","etag":"\"d9374b90a938e9923d910594731b7b57-106\"","fetched_at":"2026-09-16T00:55:27.040971Z","row_sha256":"795668ea2b16c33e8b1fe3307547d1ee90c94b933e3bf1734db94cbd3f39dd62","last_modified":"2026-09-13T14:50:39Z"},"updated_at":"2026-09-16T00:55:27.040971Z","first_seen_at":"2026-09-16T00:55:27.040971Z"},"description":{"text":"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.","origin":"extract"},"notice_type":{"code":"r","label":"Sources Sought"},"schema_version":1,"solicitation_number":"FA8612","place_of_performance":{"zip":"45433","city":{"name":"Dayton"},"state":{"code":"OH"},"country":{"code":"USA"}}},{"dates":{"posted":"2026-09-03","response_deadline":{"raw":"2026-10-09T17:00:00-04:00","utc":"2026-10-09T21:00:00Z","date":"2026-10-09","time":"17:00:00","utc_offset_seconds":-14400}},"links":{"sam":"https://sam.gov/workspace/contract/opp/9e23698488284056940cda4a0de11d1c/view"},"naics":{},"title":"Ground-Based, Medium-Caliber Gun Weapon System","agency":{"office":{"code":"FA8612","name":"FA8612 AFLCMC C3BM C3"},"subtier":{"code":"5700","name":"DEPT OF THE AIR FORCE"},"department":{"code":"057","name":"DEPT OF DEFENSE"},"office_address":{"zip":"45434-7104","city":"DAYTON","state":"OH","country":"USA"},"organization_type":"OFFICE"},"status":{"active":true,"archive_date":"2026-10-09","archive_type":"auto_custom"},"contacts":[{"name":"Christine Basham","role":"primary","email":"christine.basham.1@us.af.mil"},{"name":"Veronica Schoultz","role":"secondary","email":"veronica.schoultz@us.af.mil"}],"base_type":{"code":"r","label":"Sources Sought"},"notice_id":"9e23698488284056940cda4a0de11d1c","provenance":{"extract":{"url":"https://s3.amazonaws.com/falextracts/Contract%20Opportunities/datagov/ContractOpportunitiesFullCSV.csv","etag":"\"3f59209463433eba6899e195a597c64d-29\"","fetched_at":"2026-09-16T07:50:12.777658Z","row_sha256":"1dc9f899afbb1475264cab2c237c10aea45c3f801074b7f59054c828f1e1994c","last_modified":"2026-09-16T03:30:52Z"},"updated_at":"2026-09-16T07:50:12.777658Z","first_seen_at":"2026-09-15T22:52:52.472456Z"},"description":{"text":"SYNOPSIS The Air Force Life Cycle Management Center (AFLCMC), C3BM?Directorate,?Wright Patterson?Force Base (WPAFB),?Ohio?is conducting market research seeking vendor interest for?a?Ground-Based, Medium-Caliber Gun Weapon System. ? This is a Request?For?Information (RFI) only. This RFI is issued solely for market research purposes. It?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. Further, the Air Force (AF) is not seeking proposals, nor will it accept unsolicited proposals at this time.?? Respondents are advised that the United States Government will not pay for any information or administrative costs incurred in response to this RFI. All costs associated with responding to this RFI will be solely at the interested party’s expense. Not responding to this RFI does not?preclude?participation in any future RFP, if any is issued. It is the responsibility of the potential offerors to?monitor?the Government’s point of entry (www.sam.gov) for?additional?information?pertaining to?this requirement.? Additionally, Non-Government A&AS support may be?utilized?in the review process of RFI submissions. These non-governmental support staff are covered directly by Nondisclosure Agreements (NDAs) with the US Government as a condition of employment. Any respondent to the RFI with concern should notify one of the POCs found in Section 7.?? PURPOSE The Government is conducting market research to identify potential industry sources capable of providing solutions for a Ground-Based, Medium-Caliber Gun Weapon System that fires affordable munitions, enables defense against air and missile threats with an initial focus on subsonic cruise missiles (CM) and Unmanned Aircraft Systems (UAS) to provide persistent defense in support of United States Air Force assets. The objective of this RFI is to gather information regarding industry capability. ACQUISITION STRATEGY? The program's acquisition strategy is currently in development.? SCOPE/REQUIREMENTS The scope of this RFI is centered on solutions that strictly prioritize fifteen baseline attributes essential to operational success that can engage both cruise missiles and UAS (groups 1-5) threats in accordance with the reference documents. To effectively assess and compare air defense weapon system performance, there are fifteen critical baseline operational and technical parameters that must be analyzed in unison. These key metrics begin with the system's Salvo Probability of Kill (Pk) evaluated against both Cruise Missiles (CM) and Unmanned Aircraft Systems (UAS) Groups 1-5 at maximum range and altitude, ensuring robust lethality against diverse modern threats. The physical footprint of the engagement envelope is defined by its Effective Slant Range and Elevation Coverage, while the capacity for sustained operations is dictated by Magazine Depth and the system's ability to execute Raid Handling against saturating attacks. Furthermore, modern multi-domain operations require seamless Integrated Sensor Capability, deep C2 System Integration, and broad System Interoperability across joint networks. From an efficiency and sustainment standpoint, the system must balance its Cost Per Engagement and Manpower requirements, supported by a reliable Built-in-Test (BIT) framework for rapid diagnostics. Finally, tactical utility is rounded out by the platform's overall Transportability, stringent Weapon Safety protocols, and its comprehensive Multi-Domain Engagement Capability to counter threats across various operational environments. Fifteen Baseline Requirements: Salvo Probability of Kill (Pk) vs CM at max range and altitude Salvo Probability of Kill (Pk) vs UAS Groups 1-5 at max range and altitude Effective Slant Range Elevation Coverage Magazine Depth Raid Handling Integrated Sensor Capability C2 System Integration System Interoperability Cost Per Engagement Manpower Built-in-Test (BIT) Transportability Weapon Safety Multi-Domain Engagement Capability When designing and evaluating next-generation defense systems, the development team must navigate critical trade-offs across three primary Trade Space Attributes to balance lethality, situational awareness, and operational flexibility. First, the system must optimize Munition Performance versus Munition Cost and Gun Capability, ensuring that the interceptor's velocity, maneuverability, and terminal effects are maximized without driving the cost-per-engagement to unsustainable levels or exceeding the physical constraints of the host platform. Second, developers must carefully select the Organic Sensor Capability and Phenomenology—integrating the right mix of radar, electro-optical, infrared, or radio-frequency sensors—to ensure reliable target acquisition and tracking across varying weather conditions, environments, and countermeasure scenarios. Finally, the entire architecture must remain Rapidly Deployable, maintaining a lightweight, modular, and transportable footprint that can be swiftly projected into austere theater environments to meet emergent threats. Trade Space Attributes: Munition Performance vs. Munition Cost/Gun Capability Organic Sensor Capability and Phenomenology Rapidly Deployable RESPONSE GUIDELINES THE CONTRACTOR'S RFI RESPONSE SHALL BE: Page Limit: 10 pages or less (cover page is not included in page count) Format: Submissions must be provided in PDF Submissions must be provided in PDF?with naming convention: CompanyName_SystemName_DDMMYYYY Font: One (1)-inch margins; Times New Roman 12 font Classifications: All responses must be UNCLASSIFIED. If proprietary data is included, it must be clearly marked. Provide the following business information for your company/institution and for any teaming or joint venture partners. Company Name Address Point of Contact Unique Entity ID (UEI) CAGE Code Phone Number E-mail Address Web Page Address Specify whether your company is a U.S. or foreign-owned firm Company Size Status Business System Status Facility Clearance Level (RFP release may contain classified components.) Anticipated North American Industry Classification System Code (NAICS Code): 332994 The Government anticipates the North American Industry Classification System (NAICS) code for this effort to be 332994 - Small Arms, Ordnance, and Ordnance Accessories Manufacturing. If your organization believes another NAICS code is more appropriate for this requirement, please provide the suggested NAICS code along with a brief, objective justification supporting why the alternative code is a more accurate representation of the planned scope of work. The final NAICS determination will depend on the final acquisition strategy and selected contract vehicle. ORGANIZATIONAL CONFLICT OF INTEREST: Organizational Conflict of Interest (OCI), as defined and discussed in FAR 9.5, Organizational and Consultant Conflicts of Interest, is a concern in all acquisitions across the Department of Defense. Early involvement with our industry partners is a key element of the OCI process, and it is critical for the Government to be able to identify any potential OCI issues as early as possible for acquisition. SUBMISSION DUE DATE: 09 OCTOBER 2026, 1700, EST. Late responses may not be reviewed. SUBMISSION: Responses should be submitted electronically to the contracting officer (CO). Primary CO: Christine Basham, christine.basham.1@us.af.mil Secondary CO: Veronica Schoultz, veronica.schoultz@us.af.mil PLEASE NOTE: All interested contractors must be registered in SAM to be eligible for award of Government contracts. The Government reserves the right to consider a small business set-aside based upon responses hereto for any subsequent action. If submitting company proprietary information or competition sensitive information, please make sure it is CLEARLY MARKED. To aid the Government, please segregate proprietary information to the maximum extent possible. All segregated proprietary information will be protected by the Government. DISCLAIMER THIS IS AN RFI ONLY. The information provided in this RFI is subject to change and is not binding on the Government. The Air Force has not made a commitment to procure any of the items or services discussed above, and release of this RFI should not be construed as such a commitment or as an authorization to incur cost for which reimbursement would be required or sought. All submissions become Government property and will not be returned. QUESTIONS Any questions should be submitted to the Contracting Officer(s) as identified above. REFERENCE DOCUMENTS: Memorandum for Senior Pentagon Leadership Commanders of the Combatant Commands Defense Agency and Dod Field Activity Directors, “Guidance for the Use of Unmanned Aircraft Systems in the U.S. National Airspace”, dated 31 October 2023. Joint Publication 3-01, “Counter Air and Missile Threats”, dated 23 March 2012. https://defenseinnovationmarketplace.dtic.mil/wp-content/uploads/2018/02/JointDoctrine-CounteringAirandMissileThreats.pdf","origin":"extract"},"notice_type":{"code":"r","label":"Sources Sought"},"schema_version":1,"solicitation_number":"FA8612_"}],"due_at":"2026-10-09T21:00:00Z","due_date":"2026-10-09","closes_at":"2026-10-09T21:00:00Z","awardable":true,"dept_key":"d-057","dept_name":"DEPT OF DEFENSE","sub_key":"s-5700","sub_name":"DEPT OF THE AIR FORCE","office_key":"o-FA8612","office_name":"FA8612 AFLCMC C3BM C3","state":"OH","country":"USA","winner_key":null,"amount":null,"linked_awards":0,"cancelled":false,"archived":false,"updated_at":"2026-09-16T07:31:38.954589Z","principal_notice_id":"9e23698488284056940cda4a0de11d1c","description":{"text":"SYNOPSIS The Air Force Life Cycle Management Center (AFLCMC), C3BM?Directorate,?Wright Patterson?Force Base (WPAFB),?Ohio?is conducting market research seeking vendor interest for?a?Ground-Based, Medium-Caliber Gun Weapon System. ? This is a Request?For?Information (RFI) only. This RFI is issued solely for market research purposes. It?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. Further, the Air Force (AF) is not seeking proposals, nor will it accept unsolicited proposals at this time.?? Respondents are advised that the United States Government will not pay for any information or administrative costs incurred in response to this RFI. All costs associated with responding to this RFI will be solely at the interested party’s expense. Not responding to this RFI does not?preclude?participation in any future RFP, if any is issued. It is the responsibility of the potential offerors to?monitor?the Government’s point of entry (www.sam.gov) for?additional?information?pertaining to?this requirement.? Additionally, Non-Government A&AS support may be?utilized?in the review process of RFI submissions. These non-governmental support staff are covered directly by Nondisclosure Agreements (NDAs) with the US Government as a condition of employment. Any respondent to the RFI with concern should notify one of the POCs found in Section 7.?? PURPOSE The Government is conducting market research to identify potential industry sources capable of providing solutions for a Ground-Based, Medium-Caliber Gun Weapon System that fires affordable munitions, enables defense against air and missile threats with an initial focus on subsonic cruise missiles (CM) and Unmanned Aircraft Systems (UAS) to provide persistent defense in support of United States Air Force assets. The objective of this RFI is to gather information regarding industry capability. ACQUISITION STRATEGY? The program's acquisition strategy is currently in development.? SCOPE/REQUIREMENTS The scope of this RFI is centered on solutions that strictly prioritize fifteen baseline attributes essential to operational success that can engage both cruise missiles and UAS (groups 1-5) threats in accordance with the reference documents. To effectively assess and compare air defense weapon system performance, there are fifteen critical baseline operational and technical parameters that must be analyzed in unison. These key metrics begin with the system's Salvo Probability of Kill (Pk) evaluated against both Cruise Missiles (CM) and Unmanned Aircraft Systems (UAS) Groups 1-5 at maximum range and altitude, ensuring robust lethality against diverse modern threats. The physical footprint of the engagement envelope is defined by its Effective Slant Range and Elevation Coverage, while the capacity for sustained operations is dictated by Magazine Depth and the system's ability to execute Raid Handling against saturating attacks. Furthermore, modern multi-domain operations require seamless Integrated Sensor Capability, deep C2 System Integration, and broad System Interoperability across joint networks. From an efficiency and sustainment standpoint, the system must balance its Cost Per Engagement and Manpower requirements, supported by a reliable Built-in-Test (BIT) framework for rapid diagnostics. Finally, tactical utility is rounded out by the platform's overall Transportability, stringent Weapon Safety protocols, and its comprehensive Multi-Domain Engagement Capability to counter threats across various operational environments. Fifteen Baseline Requirements: Salvo Probability of Kill (Pk) vs CM at max range and altitude Salvo Probability of Kill (Pk) vs UAS Groups 1-5 at max range and altitude Effective Slant Range Elevation Coverage Magazine Depth Raid Handling Integrated Sensor Capability C2 System Integration System Interoperability Cost Per Engagement Manpower Built-in-Test (BIT) Transportability Weapon Safety Multi-Domain Engagement Capability When designing and evaluating next-generation defense systems, the development team must navigate critical trade-offs across three primary Trade Space Attributes to balance lethality, situational awareness, and operational flexibility. First, the system must optimize Munition Performance versus Munition Cost and Gun Capability, ensuring that the interceptor's velocity, maneuverability, and terminal effects are maximized without driving the cost-per-engagement to unsustainable levels or exceeding the physical constraints of the host platform. Second, developers must carefully select the Organic Sensor Capability and Phenomenology—integrating the right mix of radar, electro-optical, infrared, or radio-frequency sensors—to ensure reliable target acquisition and tracking across varying weather conditions, environments, and countermeasure scenarios. Finally, the entire architecture must remain Rapidly Deployable, maintaining a lightweight, modular, and transportable footprint that can be swiftly projected into austere theater environments to meet emergent threats. Trade Space Attributes: Munition Performance vs. Munition Cost/Gun Capability Organic Sensor Capability and Phenomenology Rapidly Deployable RESPONSE GUIDELINES THE CONTRACTOR'S RFI RESPONSE SHALL BE: Page Limit: 10 pages or less (cover page is not included in page count) Format: Submissions must be provided in PDF Submissions must be provided in PDF?with naming convention: CompanyName_SystemName_DDMMYYYY Font: One (1)-inch margins; Times New Roman 12 font Classifications: All responses must be UNCLASSIFIED. If proprietary data is included, it must be clearly marked. Provide the following business information for your company/institution and for any teaming or joint venture partners. Company Name Address Point of Contact Unique Entity ID (UEI) CAGE Code Phone Number E-mail Address Web Page Address Specify whether your company is a U.S. or foreign-owned firm Company Size Status Business System Status Facility Clearance Level (RFP release may contain classified components.) Anticipated North American Industry Classification System Code (NAICS Code): 332994 The Government anticipates the North American Industry Classification System (NAICS) code for this effort to be 332994 - Small Arms, Ordnance, and Ordnance Accessories Manufacturing. If your organization believes another NAICS code is more appropriate for this requirement, please provide the suggested NAICS code along with a brief, objective justification supporting why the alternative code is a more accurate representation of the planned scope of work. The final NAICS determination will depend on the final acquisition strategy and selected contract vehicle. ORGANIZATIONAL CONFLICT OF INTEREST: Organizational Conflict of Interest (OCI), as defined and discussed in FAR 9.5, Organizational and Consultant Conflicts of Interest, is a concern in all acquisitions across the Department of Defense. Early involvement with our industry partners is a key element of the OCI process, and it is critical for the Government to be able to identify any potential OCI issues as early as possible for acquisition. SUBMISSION DUE DATE: 09 OCTOBER 2026, 1700, EST. Late responses may not be reviewed. SUBMISSION: Responses should be submitted electronically to the contracting officer (CO). Primary CO: Christine Basham, christine.basham.1@us.af.mil Secondary CO: Veronica Schoultz, veronica.schoultz@us.af.mil PLEASE NOTE: All interested contractors must be registered in SAM to be eligible for award of Government contracts. The Government reserves the right to consider a small business set-aside based upon responses hereto for any subsequent action. If submitting company proprietary information or competition sensitive information, please make sure it is CLEARLY MARKED. To aid the Government, please segregate proprietary information to the maximum extent possible. All segregated proprietary information will be protected by the Government. DISCLAIMER THIS IS AN RFI ONLY. The information provided in this RFI is subject to change and is not binding on the Government. The Air Force has not made a commitment to procure any of the items or services discussed above, and release of this RFI should not be construed as such a commitment or as an authorization to incur cost for which reimbursement would be required or sought. All submissions become Government property and will not be returned. QUESTIONS Any questions should be submitted to the Contracting Officer(s) as identified above. REFERENCE DOCUMENTS: Memorandum for Senior Pentagon Leadership Commanders of the Combatant Commands Defense Agency and Dod Field Activity Directors, “Guidance for the Use of Unmanned Aircraft Systems in the U.S. National Airspace”, dated 31 October 2023. Joint Publication 3-01, “Counter Air and Missile Threats”, dated 23 March 2012. https://defenseinnovationmarketplace.dtic.mil/wp-content/uploads/2018/02/JointDoctrine-CounteringAirandMissileThreats.pdf","html":null,"origin":"extract"},"contacts":[{"name":"Christine Basham","role":"primary","email":"christine.basham.1@us.af.mil"},{"name":"Veronica Schoultz","role":"secondary","email":"veronica.schoultz@us.af.mil"}],"place_of_performance":null,"office_address":{"zip":"45434-7104","city":"DAYTON","state":"OH","country":"USA"},"naics_codes":[],"award":null,"attachments":[],"awards":[],"related":[]}