AFSOC Innovation, Logistical, and Material Support OTA

Questions & Answers / Clarifications

This document provides responses to vendor questions regarding the AFSOC-OTA-26-001 Prototype OTA solicitation, clarifying aspects of the opportunity.

• Scope of Solutions: The solicitation is flexible and allows for various capabilities and services to enhance AFSOC mission readiness, not limited to specific end-to-end solutions. The focus is on a rapid innovation pathway (concept-to-demo-to-fielding) rather than procuring a predetermined system.
• Advanced Manufacturing: The intent is to leverage advanced manufacturing (additive and subtractive) from industry, including non-GOCO organizations. However, advanced manufacturing is one segment of the overall requirements, which are generally services/support oriented.
• Place of Performance: Contractor facilities must be within 3 miles of Hurlburt Field, FL, and designated range spaces within 55 miles. This is a requirement at the time of proposal submission for rapid iteration.
• Security Clearances: While language is broad, an FCL "in the works" may be acceptable for unclassified tasks or tasks allowing performance while clearances are finalized. Classified tasks will require meeting specific security requirements defined per task order.
• In-Kind Contributions: Prototype OTAs commonly require meaningful participation beyond government funding, such as internally funded labor, facility use, or materials. This should be described in the submission and is typically managed at the task-order level.
• Facility Control: The prime offeror does not need to own the facility but must have full control of it.
• Award Structure: The government is not committing to a single or multiple award structure in advance; this will depend on submission quality and government needs.
• UAS Types: The solicitation is flexible regarding UAS classes (Group 1-2 vs. larger platforms) and will be determined at the task-order level based on mission needs.

These clarifications refine understanding of the solicitation's scope, performance locations, security requirements, and evaluation considerations, particularly regarding technical merit versus experience. Offerors should clearly articulate their capabilities and plans in light of these responses.

Questions & Answers / Clarifications

This document provides responses to vendor questions regarding the AFSOC-OTA-26-001 Prototype OTA solicitation, clarifying the scope, requirements, and evaluation criteria.

• Scope of Solutions: The solicitation is not intended to procure a specific "end-to-end" solution. The broad language allows flexibility for various support, capabilities, and services to align with AFSOC mission needs and capability gaps, enabling a rapid innovation pathway (concept-to-demo-to-fielding).
• Advanced Manufacturing: The intent is to leverage advanced manufacturing (additive and subtractive) from industry, including non-GOCO organizations. However, advanced manufacturing is only one segment of the overall requirements, which are generally services/support oriented. The mix of services vs. manufacturing will be driven by task orders.
• Place of Performance: Contractor facilities must be located within 3 miles of Hurlburt Field, Florida, and designated range spaces within 55 miles. Facilities approximately 65 miles away would not meet the stated requirement at the time of proposal submission.
• Security Clearances: While language is broad, an FCL "in the works" may be acceptable for unclassified tasks or tasks allowing performance while clearances are finalized. Specific security requirements (facility, personnel, safeguarding) will be defined per task order, and awardees must meet those requirements.
• Facility Control: The prime offeror does not need to own the facility but must have full control of it.
• Award Structure: The government is not committing to a single or multiple award structure in advance; this will depend on submission quality and government needs.
• Technical Merit vs. Experience: Lack of direct relevant experience or past performance is not automatically disqualifying but may impact evaluation. Offerors should emphasize technical merit, execution ability, risk management, and provide analogous examples or key personnel experience if direct past performance is limited.

These clarifications refine the understanding of the solicitation's scope, location requirements, security expectations, and evaluation considerations. Bidders should ensure their proposals address these points, particularly regarding facility location, security posture, and demonstrating technical merit even with limited direct past performance.

Questions & Answers / Clarifications

This document provides clarifications and answers to vendor questions regarding the AFSOC-OTA-26-001 solicitation.

• Scope of Solutions: The solicitation is designed for rapid innovation and development against AFSOC mission needs, not to procure a specific pre-determined "end-to-end" solution. While companies can propose their capabilities, the focus is on addressing AFSOC's validated mission requirements and capability gaps.
• Advanced Manufacturing: The intent is to leverage advanced manufacturing (additive and subtractive) from various organizations, not exclusively GOCO (Government-Owned, Contractor-Operated) facilities. However, advanced manufacturing is only one segment of the overall requirements, which are generally services/support oriented for rapid development.
• Place of Performance: Contractor facilities must be located within 3 miles of Hurlburt Field, Florida, and designated range spaces within 55 miles. These are requirements at the time of proposal submission to ensure rapid iteration with AFSOC teams and assets.
• Security Clearances: While the solicitation language is broad, an "FCL in the works" may be acceptable for unclassified tasks or tasks that can be performed while clearances are finalized. However, any task order requiring classified performance will necessitate meeting specific security requirements (facility, personnel, safeguarding) defined for that task.
• In-Kind Contributions: Prototype OTAs commonly require meaningful participation beyond government funding, such as internally funded labor, facility use, materials, or test support. This "skin in the game" should be described in the submission and is typically managed at the task-order level.
• Facility Control: The prime contractor does not need to own the facility, but they must have full control over it.

These clarifications do not appear to alter key requirements or submission deadlines but provide essential context for vendors regarding the nature of the innovation pathway, facility, and security requirements.

Questions & Answers / Clarifications

This document provides responses to vendor questions regarding the AFSOC-OTA-26-001 Prototype Other Transaction Authority (OTA).

• Scope of Solutions: The solicitation is not intended to procure a specific "end-to-end" solution. The broad language allows flexibility for various support, capabilities, and services to enable rapid development, demonstration, or deployment aligned with AFSOC mission needs and capability gaps. Future efforts may leverage specific company offerings if they align with defined mission requirements.
• Advanced Manufacturing: The intent is to leverage advanced manufacturing (additive and subtractive), design, fabrication, and integration from industry, including non-Government Owned Contractor Operated (GOCO) organizations. However, advanced manufacturing is only one segment of the overall requirements, which are generally services/support oriented for rapid innovation.
• Place of Performance: The 3-mile radius for contractor facilities and 55-mile radius for designated range spaces from Hurlburt Field, Florida, are tied to operational requirements for rapid iteration. These are requirements at the time of proposal submission.
• Security Clearances: While language is broad, having a Facility Clearance (FCL) "in the works" may be acceptable for unclassified tasks or tasks allowing performance while clearances are finalized. Specific security requirements (facility, personnel, safeguarding) will be defined per task order, and awardees must meet those defined requirements.
• In-Kind Contributions: Prototype OTAs commonly require meaningful participation beyond government funding, such as internally funded labor, use of facilities/equipment, materials, and test support. This should be clearly described in submissions and is typically managed at the task-order level.

These clarifications do not appear to alter key requirements or due dates but provide essential context for bidders regarding the scope, operational needs, and submission requirements for the Prototype OTA.

Questions & Answers / Clarifications

This document provides clarification on the AFSOC-OTA-26-001 Prototype Other Transaction Authority (OTA) solicitation, addressing a vendor's question regarding the scope of eligible responses.

• Vendor Question: A vendor inquired if the solicitation's broad language, "Any other capability or service required to enable the rapid development, demonstration, or deployment of solutions that enhance AFSOC mission readiness," permits responses focused on an end-to-end solution like their "SensorOS capability (end-to-end solution for LAAD)" for AFSOC mission requirements/capability gaps, rather than services/support.
• Agency Response: The Prototype OTA is not intended to solicit or select a specific "end-to-end" solution. The broad language is intended to allow flexibility in the types of support, capabilities, and services needed to align with validated AFSOC mission needs and capability gaps.
• Purpose of OTA: The OTA's purpose is to provide AFSOC a rapid innovation pathway (concept-to-demo-to-fielding), not to procure a predetermined system.
• Future Relevance: If a future prototype effort identifies a requirement where a vendor's offering is relevant, the awardee may choose to work with that company. However, this would be driven by AFSOC mission requirements as defined during the effort, not by the solicitation being an open call for complete standalone solutions.

This clarification emphasizes that the solicitation is seeking flexible solutions to address AFSOC mission needs and capability gaps, rather than specific pre-defined end-to-end systems. Vendors should focus their proposals on how their capabilities can contribute to rapid development, demonstration, or deployment in alignment with these evolving mission requirements.

Solicitation / RFP / RFQ

This is a Prototype Other Transaction Agreement (OTA) Solicitation (Number: AFSOC-OTA-26-001) issued by the Air Force Special Operations Command (AFSOC) under the authority of 10 U.S.C. § 4022 for prototype projects. AFSOC seeks rapid development and integration of innovative capabilities from industry partners, particularly encouraging non-traditional defense contractors, small businesses, and innovative commercial firms. The government may award one or multiple OTAs, with potential for follow-on production if prototype requirements are met.

The contractor shall provide flexible, turnkey support for innovation, prototyping, and experimentation. This includes:

• Procurement of materials, COTS equipment, and custom hardware.

• Logistics coordination and vendor travel.

• Access to private or controlled range spaces with safety oversight.

• On-demand technical consultation and SME support.

• Integration of emerging technologies (AI, ML, c-UAS, cyber, tactical networking).

• Design, integration, and deployment of custom tactical networks and UAS.

• Additive and subtractive manufacturing.

• Contract Type: Prototype Other Transaction Agreement (OTA).

• Period of Performance: Ordering period from March 2, 2026, to March 1, 2031.

• Place of Performance: Primarily contractor facilities or designated range spaces within 3 miles of Hurlburt Field, FL (facility) and within 55 miles of Hurlburt Field, FL (range spaces).

• Pricing: Work Orders may be cost-shared, fixed-support, or hybrid. Pricing and cost share negotiated at the Work Order level.

• Response Deadline: February 16, 2026, by 1400 CST.

• Questions Due: February 6, 2026.

• Proposal Format: Electronic PDF, not exceeding 20 pages (excluding Security Annex).

• Evaluation Criteria (in order of importance):

  1. Technical Merit
  2. Relevant Experience & Past Performance
  3. Facilities and Location

• Encourages participation from non-traditional defense contractors, small businesses, and innovative commercial firms.

• NAICS Code: 541715 (R&D in Physical, Engineering, and Life Sciences), size standard 1,000 employees.

• This agreement is not subject to FAR/DFARS unless specifically incorporated.

• Some task orders may involve classified information up to TOP SECRET/SCI. Offerors must demonstrate capability to support classified efforts.

• Attachments referenced: Attachment 1 (PWS), Attachment 2 (Security Annex Template).

Statement of Work (SOW) / Performance Work Statement (PWS)

To provide agile and scalable acquisition support for Air Force Special Operations Command (AFSOC) to rapidly design, develop, test, and integrate innovative capabilities that enhance operational readiness and meet emerging mission demands. This includes advancing architectures for the high-end fight, enabling enhanced precision effects, supporting the Adaptive Airborne Enterprise (A2E), and accelerating force modernization.

The contractor shall provide flexible, turnkey support for innovation, prototyping, and experimentation. Key areas include:

• Procurement of materials, COTS equipment, and custom fabrication.
• Logistics coordination and vendor travel.
• Access to private or controlled range spaces and safety oversight.
• On-demand technical consultation, SME support, and lab/fabrication access.
• Integration of emerging technologies (AI, ML, c-UAS, cyber, tactical mission networking).
• Design, integration, and deployment of custom tactical networks and datalinks.
• Design, fabrication, integration, and operational employment of tactical UAS.
• Additive and subtractive manufacturing for rapid prototyping and limited-run fabrication.
• Any other service to enable rapid development, demonstration, or deployment of solutions enhancing AFSOC mission readiness. Specific work orders will define deliverables, security requirements, and performance expectations.

Not explicitly detailed in this document; will be defined in each Work Order (WO).

• Period of Performance: 2 March 2026 – 1 March 2031

• Place of Performance: Primarily off-site of Hurlburt Field, Florida, at contractor facilities or designated range spaces. Contractor facilities should be within 3 miles of Hurlburt Field; designated range spaces within 55 miles.

• Security: Some work orders may involve classified information up to TOP SECRET. Contractor personnel must possess appropriate clearances. Compliance with 32 CFR Part 117 and NISPOM is required.

• Contract Type: Other Transaction Authority (OTA).

• Pricing: Proposed by the contractor at the time of Work Order Request (WOR).

• Data Rights: Tailored at the WOR level.

• Cost Share: At least one-third of the total cost of the prototype project must be funded by non-Federal sources.

Form / Attachment / Pricing Sheet

This document is a template for an Offeror Security Annex, to be submitted for evaluation purposes. Its submission demonstrates an Offeror's capability to support classified work. Submission does not grant access to classified information or approval to perform classified work.

Offerors must provide details on the following:

• Facility Clearance (FCL) Status: Current clearance level, Cognizant Security Agency (CSA)/Defense Counterintelligence and Security Agency (DCSA), CAGE Code, and eligibility/timeline for obtaining an FCL if none exists.
• Personnel Security Clearances: Number of personnel with active Secret and Top Secret clearances, current SCI eligibility and accesses, and the process for onboarding cleared personnel.
• Secure Facilities and Classified Workspaces: Availability of secure facilities (e.g., SCIFs), whether Government-provided or contractor-owned, location relative to Hurlburt Field, FL, accreditation status, and ability to access Government-provided facilities.
• Classified Information Handling Procedures: Procedures for safeguarding classified information, compliance with 32 CFR Part 117 (NISPOM), and information system protections.
• Subcontractor and Teaming Security: Identification of subcontractors/teammates supporting classified work, their clearance status, and processes for flowing down security requirements.
• Limitations, Risks, and Mitigations: Known limitations related to classified work and mitigation strategies.
• Points of Contact: Facility Security Officer (FSO) and alternate security point of contact information.

This annex is crucial for bidders intending to perform classified work under the opportunity. It requires detailed information about the Offeror's security posture, personnel clearances, facilities, and procedures. Failure to adequately address these security requirements may impact the ability to be considered for classified task orders.