Request for Whitepapers: AEDC Velocity Alliance - A Multi-Billion Dollar OTA Consortium Opportunity

Questions & Answers / Clarifications

This document provides responses to industry partner questions regarding the Request for White Papers (RFWP) for membership in the AEDC Velocity Alliance OTA Consortium.

• Consortium Management: The government will manage the consortium internally.
• Asphalt Paving: Standalone paving projects may be competed within the Alliance under the "General Construction" category.
• Partnership Requirements: To join the Alliance, whitepaper submissions must identify a partner that meets specific statutory definitions (Non-Traditional Defense Contractor, Small Business, or Nonprofit Research Institution). University partners are highly likely to qualify as nonprofit research institutions.
• Small Business Prime Contractors: Companies that already qualify as small businesses must still identify at least one partner (NDC, university, or another small business) to demonstrate partnership capability, not just their own status.
• Project Opportunity Announcements (POAs): All consortium members will receive all POAs, regardless of demonstrated competencies. The government will not filter or limit distribution.
• CMMC Level 2 Certification: A roadmap demonstrating achievement of full CMMC Level 2 C3PAO Certification by November 2026 is a hard prerequisite for vendors relying on the alternative compliance path. Submissions with roadmaps targeting certification after November 2026 will not be considered responsive.
• Whitepaper Submission Length: The entire whitepaper submission (Parts 1-4) must not exceed ten pages. A cover page is not required and counts towards the limit if included.
• Project Examples for Technical Competency: Only completed projects within the last five years will be considered for evaluating technical competency. Ongoing or incomplete projects will not be evaluated and should not be included in Part 2 of the whitepaper.

These clarifications provide essential guidance for vendors preparing their whitepaper submissions, particularly regarding partnership requirements, CMMC compliance, and submission content and format. They emphasize the importance of demonstrating partnership capability and meeting strict cybersecurity deadlines.

Questions & Answers / Clarifications

This document provides responses to industry questions regarding the "Request for Whitepapers for Membership in the AEDC Velocity Alliance" (RFWP).

• Consortium Management: The government will manage the consortium internally.
• Asphalt Paving: Standalone paving projects may be competed within the Alliance under the "General Construction" category.
• Alliance Membership Requirements: To join the Alliance, prospective members must identify a partner that is a Non-Traditional Defense Contractor (NDC), a Small Business, or a Nonprofit Research Institution. University partners are highly likely to qualify as nonprofit research institutions.
• Small Business Prime Contractors: Even if a company qualifies as a small business, it must still identify at least one partner (NDC, university, or National Laboratory) to meet the "Innovation and Partnership Capability" requirement. This requirement focuses on demonstrating the ability to form innovative teams, not just the company's own status.
• Project Opportunity Announcements (POAs): All consortium members will receive all POAs, regardless of their demonstrated competencies. The government will not filter or limit distribution.
• Competition Process: Project competitions will be tailored to the specific requirement and may utilize various methods, including whitepapers, prototype proposals, or oral presentations. Evaluation will generally be Best Value, not Lowest Price Technically Acceptable (LPTA).
• Whitepaper Submission Length: The entire whitepaper submission (Parts 1-4) must not exceed ten pages. A cover page is not required and counts towards the limit if included.
• CMMC Requirements: A current NIST SP 800-171 DoD Assessment posted in SPRS and a detailed CMMC Level 2 roadmap are required. The roadmap must show achievement of full CMMC Level 2 C3PAO Certification by November 2026; a roadmap showing certification after this date will not be considered responsive.
• Project Examples: Projects will include infrastructure sustainment, restoration, and modernization, with examples in Process Systems, Electrical Infrastructure, Specialized Construction, and Engineering Services.
• Number of Seat Holders: There is no pre-determined or capped number of "seat holders." The goal is to onboard as many highly qualified vendors as possible to ensure a broad ecosystem of specialists and facilitate teaming.
• Site Visits: Mandatory site visits will be conducted in group settings, not individually.
• Transition to FARM III: Designs completed under the Alliance may transition to FARM III or similar FAR-based vehicles for follow-on construction if finalized and deemed ready for large-scale construction.
• CMMC Level 2 for Prime Member: For the initial whitepaper submission, only the prime member needs to provide proof of CMMC Level 2 certification or the alternative NIST+Roadmap path. However, prime members are responsible for ensuring their subcontractors meet CMMC requirements before sharing CUI or FCI.

These clarifications provide essential details for vendors preparing their whitepaper submissions, particularly regarding partnership requirements, submission formats, and cybersecurity compliance deadlines.

Questions & Answers / Clarifications

This document provides answers to industry partner questions regarding the Request for White Papers (RFWP) for membership in the AEDC Velocity Alliance OTA Consortium. It clarifies requirements for whitepaper submissions, partnership criteria, CMMC compliance, and project competition.

• Consortium Management: The Government will manage the AEDC Velocity Alliance OTA Consortium internally.
• Asphalt Paving: Standalone paving projects may be competed within the Alliance under the "General Construction" category.
• Partnership Requirements: Whitepaper submissions must identify a partner that meets specific statutory definitions (Non-Traditional Defense Contractor, Small Business, or Nonprofit Research Institution). University partners are highly likely to qualify as nonprofit research institutions. Even if a company is a small business, it must still identify at least one partner to demonstrate partnership capability.
• Whitepaper Submission Length: The entire whitepaper submission (Parts 1-4) must not exceed ten pages. A separate cover page is not required and counts towards the page limit.
• CMMC Requirement: A current NIST SP 800-171 DoD Assessment and a detailed CMMC Level 2 roadmap are required. The roadmap must show achievement of full CMMC Level 2 C3PAO Certification by November 2026; a roadmap reflecting certification after this date will not be considered responsive.
• Project Opportunity Announcements (POAs): All POAs will be disseminated to all consortium members in good standing, not via invitation only. There is no minimum number of bids required to sustain membership.
• Project Competition: Projects will generally be evaluated on a Best Value basis, not Lowest Price Technically Acceptable (LPTA). Firm-Fixed-Price (FFP) milestone-based payment structures are generally preferred for Project-Level Agreements.
• Transition to FARM III: Designs completed under the Alliance may be transitioned to FARM III or similar FAR-based vehicles for follow-on production or construction, or remain within the Alliance.
• Site Visits: Mandatory site visits will be conducted in group settings, not individually.
• Completed Projects: Responses must be based on completed projects within the last five years; ongoing or incomplete projects will not be considered.

These clarifications provide essential details for vendors preparing their whitepaper submissions, particularly regarding partnership requirements, CMMC compliance deadlines, and the structure of the consortium and future competitions. Vendors must ensure their submissions meet all specified criteria to be considered responsive.

Questions & Answers / Clarifications

This document provides responses to industry questions regarding the Request for White Papers (RFWP) for membership in the AEDC Velocity Alliance OTA Consortium. It clarifies requirements for whitepaper submissions, partnership capabilities, CMMC compliance, and project competition.

• Consortium Management: The government will manage the consortium internally.
• Asphalt Paving: Standalone paving projects may be competed within the Alliance under the "General Construction" category.
• Alliance Membership Requirements: All prospective members must identify a partner that is a Non-Traditional Defense Contractor (NDC), a Small Business, or a Nonprofit Research Institution. This requirement applies even if the prime contractor is already a small business, as the goal is to demonstrate partnership capability.
• Whitepaper Submission: The entire whitepaper submission is limited to ten pages. A cover page is not required and, if included, counts towards the page limit. Submissions must include CMMC compliance statements, company name/CAGE code, technical responses, IP acknowledgement, and partnership capability details.
• CMMC Level 2 Certification: Full CMMC Level 2 C3PAO Certification by November 2026 is a hard prerequisite for any vendor relying on the alternative compliance path. Roadmaps reflecting certification after this date will not be considered responsive.
• Project Opportunity Announcements (POAs): All consortium members in good standing will receive all POAs, regardless of demonstrated competencies. POAs will not be filtered or limited.
• Competition Process: Projects will generally be evaluated on a Best Value basis, with Firm-Fixed-Price (FFP) milestone-based payment structures being the predominant arrangement. Specific evaluation processes and agreement types will be detailed in each POA.
• Small Business Entry: Small businesses are strongly encouraged to join as prime members on their own, provided they can demonstrate the ability to partner with an NDC, nonprofit research institution, or another small business.

This Q&A document clarifies key aspects of the whitepaper submission process and alliance membership requirements, directly impacting how potential vendors must prepare and submit their applications. It emphasizes the importance of demonstrating partnership capability and meeting strict CMMC compliance deadlines.

Questions & Answers / Clarifications

This document provides responses to industry questions regarding the Request for White Papers (RFWP) for membership in the AEDC Velocity Alliance OTA Consortium.

• Consortium Management: The government will manage the consortium internally.
• Asphalt Paving: Standalone asphalt paving projects may be competed within the Alliance under the "General Construction" category.
• Alliance Membership Requirements: To join the Alliance, prospective members must identify a partner that is either a Non-Traditional Defense Contractor (NDC), a Small Business, or a Nonprofit Research Institution. University partners are highlighted as excellent candidates for meeting the "nonprofit research institution" requirement.
• Small Business Prime Contractors: Even if a company qualifies as a small business, it must still identify at least one partner (NDC, university, or another small business) to demonstrate partnership capability, not just its own status.
• Project Opportunity Announcements (POAs): All consortium members will receive all POAs, regardless of their demonstrated competencies during onboarding. There will be no filtering or sub-pools.
• Competition Process: Project competitions will be tailored to each requirement, with a strong preference for Best Value evaluations over Lowest Price Technically Acceptable (LPTA). Firm-Fixed-Price (FFP) structures are generally favored.
• CMMC Requirement: A current NIST SP 800-171 assessment and a detailed CMMC Level 2 roadmap are required. The roadmap must show achievement of full CMMC Level 2 C3PAO Certification by November 2026; a roadmap reflecting certification after this date will not be considered responsive.
• Project Examples: Projects will fall under 15 technical categories, including Process Systems, Electrical Infrastructure, Specialized Construction, and Engineering Services. Specific project examples will be provided during mandatory site visits.
• Submission Length: The entire whitepaper submission is limited to ten pages, including all four parts. A separate cover page is not required and will count towards the page limit if included.
• Completed Projects: For technical competency evaluation, only projects completed within the last five years will be considered.

These clarifications provide essential details for vendors preparing their whitepaper submissions, particularly regarding partnership requirements, submission format, and security compliance (CMMC).

Questions & Answers / Clarifications

This document provides answers to industry questions regarding the Request for White Papers (RFWP) for membership in the AEDC Velocity Alliance Consortium.

• Consortium Management: The government will manage the consortium internally.
• Asphalt Paving: Standalone asphalt paving projects may be competed within the Alliance under the "General Construction" category.
• Partnership Requirements: All prospective members must identify a partner that meets specific statutory definitions (Non-Traditional Defense Contractor, Small Business, or Nonprofit Research Institution). University partners are highly likely to qualify as nonprofit research institutions. Even if a company qualifies as a small business, it must still partner with another entity (NDC, university, or small business) to demonstrate partnership capability.
• Whitepaper Submission: The entire whitepaper submission (Parts 1-4) must not exceed ten pages. A cover page is not required and will count towards the page limit if included.
• CMMC Requirement: A current NIST SP 800-171 DoD Assessment posted in SPRS and a detailed CMMC Level 2 compliance roadmap are required. The roadmap must show full CMMC Level 2 C3PAO Certification by November 2026; a roadmap reflecting certification after this date will not be considered responsive.
• Project Opportunity Announcements (POAs): All POAs will be issued to all consortium members, regardless of demonstrated competencies during onboarding.
• Project Competition: Projects will generally be evaluated on a Best Value basis, with a preference for Firm-Fixed-Price (FFP) milestone-based structures. The specific evaluation process and agreement type will be defined in each POA.
• Transition to FARM III: Designs or "proofs of concept" completed under the Alliance may be transitioned to FARM III or similar FAR-based vehicles for subsequent construction or implementation.
• CUI Handling: All projects executed under this Alliance are expected to involve Controlled Unclassified Information (CUI), making CMMC Level 2 certification a foundational, enterprise-level security standard for all members.

Clarifies requirements for whitepaper submissions, partnership criteria, CMMC compliance, and future project competition processes, directly impacting how vendors prepare and submit their applications for Alliance membership.

Questions & Answers / Clarifications

This document provides responses to industry partner questions regarding the AEDC Velocity Alliance Request for Whitepaper (RFWP).

• Consortium Management: The government will manage the AEDC Velocity Alliance consortium internally.
• Asphalt Paving: Standalone asphalt paving projects may be competed within the Alliance under the "General Construction" category.
• Partnership Requirements: To join the Alliance, whitepapers must identify a partner that meets the statutory definition of a Non-Traditional Defense Contractor (NDC), a Small Business, or a Nonprofit Research Institution. University partners are generally considered nonprofit research institutions and are a strong fit.
• Small Business Prime Contractors: Even if a company qualifies as a small business, it must still identify at least one partner (NDC, university, or another small business) to demonstrate partnership capability, not just its own status.
• Project Opportunity Announcements (POAs): All consortium members will receive all POAs, regardless of their demonstrated competencies. There will be no filtering or sub-pools.
• Down-Selection: The government may use various methods (whitepapers, proposals, oral presentations) to down-select performers for specific projects, with details provided in each POA.
• Whitepaper Submission Length: The entire whitepaper submission (Parts 1-4) is limited to ten pages. A cover page is not required and, if included, counts towards the page limit.
• Controlled Unclassified Information (CUI): CUI may be included in whitepaper submissions, but classified information is strictly prohibited.
• CMMC Level 2 Certification: A roadmap demonstrating achievement of full CMMC Level 2 C3PAO Certification by November 2026 is a hard prerequisite for vendors using the alternative compliance path. Roadmaps showing certification after November 2026 will not be considered responsive.
• Projected Pipeline: The government forecasts approximately 135 planned projects totaling $550 million for FY26-FY27, with the Alliance serving as a vehicle for a multi-billion dollar modernization portfolio through FY32.
• Project Types: Projects will cover a diverse portfolio of infrastructure sustainment, restoration, and modernization, detailed in Attachment 1 of the RFWP.
• Number of Seat Holders: There is no pre-determined or capped number of "seat holders." The objective is to onboard as many highly qualified vendors as possible to ensure a broad industrial base.
• Site Visits: Mandatory site visits will be conducted in group settings, not individually.
• Evaluation and Contract Type: Projects will generally be evaluated on a Best Value basis, with a preference for Firm-Fixed-Price (FFP) milestone-based structures. Specifics will be detailed in each POA.
• Transition to FARM III: Designs completed under the Alliance may be transitioned to FARM III or similar vehicles for follow-on construction, or remain within the Alliance for continued operational utility.
• Submission Deadline: The June 1 submission is due by Central Daylight Time (CDT).

These Q&As provide critical clarifications on partnership requirements, submission details, security mandates (CMMC), and the overall operational framework of the AEDC Velocity Alliance, directly impacting how vendors should prepare and submit their whitepapers.

Questions & Answers / Clarifications

This document provides answers to industry partner questions regarding the Request for White Papers (RFWP) for membership in the AEDC Velocity Alliance Consortium.

• Consortium Management: The government will manage the consortium internally.
• Asphalt Paving: Standalone paving projects can be competed within the Alliance under the "General Construction" category.
• Partnership Requirements: To join the Alliance, whitepapers must identify a partner that is either a Non-Traditional Defense Contractor (NDC), a Small Business, or a Nonprofit Research Institution. University partners are highly likely to qualify as nonprofit research institutions.
• Small Business Requirement: Even if a company qualifies as a small business, it must still identify a partner (NDC, university, or another small business) to demonstrate partnership capability, not just its own status.
• Opportunity Distribution: All consortium members will receive all Project Opportunity Announcements (POAs) regardless of their demonstrated competencies. The government will not filter or limit solicitations based on onboarding phase assessments.
• Down-Selection Methods: The government may use various methods (whitepapers, prototype proposals, oral presentations, etc.) to down-select performers for specific requirements, tailored to each project's needs.
• Whitepaper Length: The entire whitepaper submission (Parts 1-4) must not exceed ten pages. A separate cover page is not required and counts towards the page limit if used.
• CUI Inclusion: Controlled Unclassified Information (CUI) may be included in whitepaper submissions, but classified information is strictly prohibited.
• CMMC Level 2 Certification: A roadmap demonstrating the plan to achieve full CMMC Level 2 C3PAO Certification by November 2026 is a hard prerequisite for vendors relying on the alternative compliance path. Roadmaps indicating certification after November 2026 will not be considered responsive.

These clarifications provide essential details for vendors preparing their whitepaper submissions, particularly regarding partnership requirements, submission format, and critical security compliance deadlines (CMMC Level 2).

Form / Attachment / Pricing Sheet

This document, titled "Atch 2 - AEDC Velocity Alliance Base Articles - 21 Apr 26.pdf", appears to be a foundational document outlining the "Article Definitions" and various articles governing an "Other Transaction (OT) Agreement" under the AEDC Velocity Alliance Consortium. It serves to define key terms and establish the framework for agreements within the alliance.

• Article Definitions: Provides definitions for terms such as Acceptance, Acceptance Criteria, Agreement, Agreements Officer (AO), Controlled Unclassified Information (CUI), Cyber Incident, Cybersecurity Maturity Model Certification (CMMC), Force Majeure, Government-Furnished Property (GFP), Milestone, Statement of Objectives (SOO)/Statement of Work (SOW), and others.
• Demonstration and Acceptance: Outlines the process for demonstrating, verifying, and formally accepting prototype deliverables.
• Agreement Modifications: Details how changes to the agreement are proposed, formalized, and handled.
• Dispute Resolution: Establishes procedures for collaborative dispute resolution, including initial resolution, senior-level escalation, and alternative dispute resolution (ADR).
• Intellectual Property Indemnification: Defines the performer's responsibility to indemnify the government against infringement claims.
• Payment and Invoicing: Specifies payment terms, invoicing procedures (via WAWF), and final payment conditions.
• Cybersecurity Requirements: Mandates compliance with NIST SP 800-171 and Cybersecurity Maturity Model Certification (CMMC) Level 2.
• Prohibited Sources: Lists specific telecommunications equipment and services that are prohibited.
• Phased Execution and Optional Milestones: Describes the anticipated phased approach to the project and the process for handling future "Options."

This document is crucial for any potential bidder or member of the AEDC Velocity Alliance as it lays out the fundamental terms and conditions governing their participation and any subsequent agreements. Understanding these articles is essential for comprehending the rights, responsibilities, and requirements associated with performing work under the alliance, including cybersecurity mandates, payment structures, dispute resolution, and intellectual property rights.

Other / Unclassified

This document outlines the objectives and scope of work for the Arnold Engineering Development Complex (AEDC) Velocity Alliance Program. The program aims to sustain and advance AEDC's infrastructure to meet current and future aerospace and defense system test and evaluation requirements. Projects will focus on improvement, modernization, restoration, and maintenance of critical test assets and supporting utilities.

This document provides potential bidders with an overview of the types of projects AEDC undertakes. It details various project categories, including:

• General Construction: Standard building structures, renovations, analysis, planning, design, procurement, fabrication, installation, demolition, and verification.
• Industrial Construction: Buildings and structures with industrial features, including test areas and integrated heavy equipment.
• Low Pressure Process Systems: Piping and equipment operating at or below 150 PSIG.
• High Pressure Process Systems: Piping and equipment operating above 150 PSIG.
• Hazardous Process Systems: Systems handling flammable or toxic media.
• Process Ducting: Large-scale process ducting (over 24 inches).
• High Voltage Electrical: Electrical systems rated above 6.9kV.
• Medium Voltage Electrical: Electrical systems rated between 600V and 6.9kV.
• Low Voltage Electrical: Electrical systems rated at 600V or less.
• Fire Suppression: Dedicated fire suppression systems.
• Equipment Repair: Repair and restoration of existing equipment.
• Mechanical Engineering Services: Non-standard and complex mechanical components.
• Electrical Engineering Services: Non-standard and complex electrical systems.
• ID&C Engineering Services: Instrumentation, Data, and Control (ID&C) systems.
• Utilities: Utility distribution systems (e.g., raw water, steam).

The document also lists potential performance locations, including Holloman Air Force Base, Arnold Air Force Base, Tunnel 9 (Silver Spring, MD), and the National Full-Scale Aerodynamics Complex (NFAC) at Moffett Field, CA. It indicates that other Air Force Test Center (AFTC) enterprise installations may also leverage this vehicle. This information helps bidders identify relevant opportunities and understand the breadth of AEDC's infrastructure needs.

Amendment / Modification

This document is Amendment 1 to the Request for Whitepapers for Membership in the AEDC Velocity Alliance. It does not introduce new requirements or change the core purpose of the original solicitation. Instead, it serves to update information and clarify the process for potential members.

• The document title indicates it is an amendment.

• The date of the memorandum is updated to "21 Apr 26".

• The content of the document details the establishment of the AEDC Velocity Alliance, a strategic consortium-based initiative by the Department of the Air Force through the Air Force Test Center (AFTC) and Arnold Engineering Development Complex (AEDC).

• It outlines the purpose of the Alliance: to create a streamlined and agile industrial partnership for accelerating sustainment, restoration, and modernization of critical test infrastructure.

• It details the multi-step onboarding and selection process for vendors, including whitepaper submission, government evaluation, mandatory site visits, and execution of a membership agreement.

• Mandatory certification requirements, including Joint Certification Program (JCP) and Cybersecurity Maturity Model Certification (CMMC) (or alternative compliance path), are specified.

• Technical competency is evaluated through responses to specific project type questions.

• Intellectual Property Rights acknowledgement and Innovation and Partnership Capability sections are outlined.

• The whitepaper evaluation criteria are detailed, including mandatory certification requirements, technical competency, IP rights acknowledgement, and innovation/partnership capability.

• The Statement of Understanding section clarifies foundational framework, mandatory site visits, ongoing cybersecurity compliance (including CMMC Level 2 deadline), and project-level impact.

• Submission schedule and key information, including whitepaper submission deadlines, contact information, and a process flow diagram, are provided.

• Onboarding phases and associated deadlines for whitepaper responses and mandatory site visits are listed.

• This amendment does not appear to change any proposal deadlines or submission requirements from the original solicitation. It clarifies and provides updated information regarding the process for vendors to become members of the AEDC Velocity Alliance.

Questions & Answers / Clarifications

This document provides responses to industry questions regarding the Request for White Papers (RFWP) for membership in the AEDC Velocity Alliance OTA Consortium.

• Consortium Management: The government will manage the consortium internally.
• Asphalt Paving: Standalone paving projects can be competed within the Alliance under the "General Construction" category.
• Partnership Requirements: To join the Alliance, prospective members must identify a partner that is a Non-Traditional Defense Contractor (NDC), a Small Business, or a Nonprofit Research Institution. University partners are highly likely to qualify as nonprofit research institutions.
• Small Business Prime Contractors: Even if a company qualifies as a small business, it is still required to identify at least one partner (NDC, university, or another small business) to demonstrate partnership capability. The focus is on the ability to build effective teams.
• Whitepaper Submission: The entire whitepaper submission (Parts 1-4) must not exceed ten pages. A separate cover page is not required and counts towards the page limit if used.
• CUI Inclusion: Controlled Unclassified Information (CUI) may be included in whitepaper submissions, but classified information is strictly prohibited.
• CMMC Level 2 Certification: A roadmap reflecting achievement of full CMMC Level 2 certification after November 2026 will not be considered responsive. A viable roadmap to achieve certification by November 2026 is a hard prerequisite for the alternative compliance path.

These clarifications provide essential guidance for potential members preparing their whitepaper submissions, particularly regarding partnership requirements, submission format, and critical security compliance deadlines.

Questions & Answers / Clarifications

This document provides responses to industry questions regarding the Request for White Papers (RFWP) for membership in the AEDC Velocity Alliance OTA Consortium.

• Consortium Management: The government will manage the consortium internally.
• Asphalt Paving: Standalone asphalt paving projects may be competed within the Alliance under the "General Construction" category.
• Alliance Membership Requirements: To join the Alliance, prospective members must demonstrate an established relationship with a Non-Traditional Defense Contractor (NDC), a Small Business, or a Nonprofit Research Institution. This requirement applies even if the prime contractor is already a small business. The purpose is to assess the company's capability to form innovative partnerships.
• Partner Identification: Whitepapers must identify a partner (NDC, university, or small business) by name and CAGE code, and explain how their capabilities link to the technical project and would participate significantly.
• Future Solicitations: All consortium members will receive all Project Opportunity Announcements (POAs) regardless of their demonstrated competencies during onboarding. The government will not filter or limit solicitations.
• Down-Selection Methods: The government may use various methods for down-selecting performers for specific requirements, including white papers, prototype proposals, or oral presentations, tailored to the needs of each project.
• White Paper Length: The entire white paper submission (Parts 1-4) must not exceed ten pages. A separate cover page is not required and will count towards the page limit if included.
• CUI Inclusion: Controlled Unclassified Information (CUI) may be included in white paper submissions, but classified information is strictly prohibited.
• Submission Method: Submissions are to be sent directly via standard email, not through the DoD SAFE application. Compliance with CMMC Level 2 or NIST SP 800-171 is required for electronic transmission.

These clarifications provide essential details for potential members preparing their white papers, particularly regarding partnership requirements, submission format, and length. They emphasize the need to demonstrate partnership capability and adherence to specific submission guidelines.

Questions & Answers / Clarifications

This document provides responses to industry partner questions regarding the AEDC Velocity Alliance Request for Whitepaper (RFWP).

• Consortium Management: The government will manage the AEDC Velocity Alliance OTA Consortium internally.
• Asphalt Paving: Standalone asphalt paving projects can be competed within the Alliance under the "General Construction" category.
• Partnership Requirements: To join the Alliance, prospective members must identify a partner that is either a Non-Traditional Defense Contractor (NDC), a Small Business, or a Nonprofit Research Institution. This requirement applies even if the prime contractor is already a small business. The purpose is to demonstrate partnership capability, not just company status.
• University/Lab Partners: Universities are strong candidates as "nonprofit research institutions." National Laboratories may also qualify. Whitepapers should identify a partner by name and CAGE code, explain the existing relationship, and detail how their capabilities align with technical projects.
• Small Business Partners: If a small business partners with another small business, they must demonstrate how this partnership satisfies the statutory requirement for "significant participants" being small businesses.
• Opportunity Distribution: All consortium members will receive all Project Opportunity Announcements (POAs) regardless of their demonstrated competencies. The Alliance aims for a fair and open ecosystem.
• Down-Selection Methods: The government will use the most efficient means to select performers for projects, which may include whitepapers, prototype proposals, oral presentations, or other methods defined in the POA.

This Q&A document clarifies partnership requirements and opportunity distribution for the AEDC Velocity Alliance whitepaper submission. It emphasizes the need to demonstrate team-building capabilities and assures all members will have visibility into all future solicitations.

Questions & Answers / Clarifications

This document provides responses to industry partner questions regarding the AEDC Velocity Alliance OTA Consortium Request for Whitepaper.

• Consortium Management: The government will manage the consortium internally.

• Asphalt Paving: Standalone asphalt paving projects could be competed within the AEDC Velocity Alliance under the "General Construction" category.

• Alliance Membership Requirements: To join the Alliance, prospective members must identify a partner that meets specific statutory definitions. This partner must be either:

  • A Non-Traditional Defense Contractor (NDC)
  • A Small Business
  • A Nonprofit Research Institution
  • University partners are highly likely to qualify as nonprofit research institutions.
  • National Laboratories may also qualify, but leveraging university partnerships is presented as a more direct path.

• Small Business Prime Contractors: Even if a company qualifies as a small business, it is still required to identify at least one partner (NDC, university, or another small business) to demonstrate partnership capability. The requirement focuses on the ability to form innovative and effective teams, not just the prime contractor's status.

• The clarifications provide specific guidance on how to meet the partnership requirements outlined in "Part 4: Innovation and Partnership Capability" of the Request for Whitepaper (RFWP).

• Bidders are instructed to select a partner, provide their name and CAGE code, and explain how their capabilities link to the technical project and would participate significantly. This guidance is crucial for whitepaper submissions.

Questions & Answers / Clarifications

This document provides answers to industry partner questions regarding the AEDC Velocity Alliance Request for Whitepaper (RFWP).

• Consortium Management: The government will manage the AEDC Velocity Alliance consortium internally.
• Asphalt Paving: Standalone asphalt paving projects are not included in the current scope but could potentially be competed within the Alliance under a "General Construction" category.
• Alliance Membership Requirements: To join the Alliance, prospective members must identify a partner that meets specific statutory definitions. This partner must be either:
  • A Non-Traditional Defense Contractor (NDC)
  • A Small Business
  • A Nonprofit Research Institution
  • A University Partner (which typically qualifies as a nonprofit research institution)
  • A National Laboratory (which may qualify as a nonprofit research institution)
• Whitepaper Submission Guidance: For whitepaper submissions, the strongest approach is to:
  1. Feature one university partner in the "Part 4: Innovation and Partnership Capability" response.
  2. Provide the university's name and CAGE code, justifying how they meet the statutory requirements (10 U.S.C. § 4022(d)(1)(A) or (B)).
  3. Describe the existing relationship and the partner's unique capabilities, linking them directly to the technical project described in "Part 2" of the whitepaper.

This Q&A clarifies partnership requirements and provides specific guidance for whitepaper submissions, particularly concerning the identification and justification of eligible partners. It does not appear to alter any deadlines or core submission rules, but it refines the expected content for the partnership section of the whitepaper.

Solicitation / RFP / RFQ

This document is a Request for Whitepapers to solicit expertise for membership in the AEDC Velocity Alliance. The Alliance is a strategic, consortium-based initiative established by the Department of the Air Force (through AFTC and AEDC) under 10 U.S.C. § 4022 to accelerate the sustainment, restoration, and modernization of critical test infrastructure. The goal is to create a streamlined and agile industrial partnership to support the development and validation of next-generation national defense systems. Projects awarded under this initiative will be competed exclusively among Alliance members.

• Vendors must submit a whitepaper demonstrating their capabilities.

• Whitepapers will be evaluated based on mandatory certifications and technical competency.

• Mandatory certifications include Joint Certification Program (JCP) and Cybersecurity Maturity Model Certification (CMMC) Level 2 (or an alternative compliance path involving NIST SP 800-171 assessment and a CMMC roadmap).

• Technical competency will be assessed through detailed responses to specific project-type questions.

• Vendors must also demonstrate innovation and partnership capability, potentially involving nontraditional defense contractors (NDCs) or small businesses.

• This is a Request for Whitepapers for membership in the Alliance, not a direct contract award.

• Individual projects will be competed among Alliance members via Project-Level Agreements.

• The Government anticipates investing multi-billion dollars in test infrastructure at AEDC through Fiscal Year 2032.

• Whitepapers are due by specific dates for different onboarding opportunities (e.g., Opportunity 1: 1 June 2026).

• Submissions must be in PDF format, not exceeding ten pages.

• Evaluation is a four-part Pass/Fail process: Mandatory Certifications, Technical Competency, Intellectual Property Rights Acknowledgement, and Innovation/Partnership Capability.

• Vendors who successfully pass all four parts will be invited to a mandatory site visit.

• Final membership is contingent upon successful completion of the site visit and execution of a Membership Agreement.

• The document does not specify set-asides for this whitepaper submission phase.

• However, the Innovation and Partnership Capability section requires demonstration of ability to partner with NDCs or small businesses.

• This is an unfunded solicitation; vendors are responsible for all costs associated with participation.

• The Alliance is expected to become active on 1 July 2026.

• Governing documents (SOO and Base Articles) are considered "living documents" and subject to change.

• Vendors must acknowledge and agree to the terms outlined in the Statement of Understanding, including ongoing cybersecurity compliance and mandatory site visits.

Other / Unclassified

This document is a Memorandum for AEDC Velocity Alliance Consortium Members, dated March 5, 2026. It provides definitions for terms used throughout the "Agreement," which is identified as an Other Transaction (OT) Agreement executed under the authority of 10 U.S.C. § 4022. The memorandum details various terms such as Acceptance, Acceptance Criteria, Agreement, Agreements Officer (AO), CUI, Cyber Incident, CMMC, Force Majeure, Government-Furnished Property (GFP), Milestone, Statement of Work (SOW), and others.

It also outlines articles related to Demonstration and Acceptance, Assignment of Payments, Agreement Modifications, Collaborative Dispute Resolution, Excusable Delays, Intellectual Property Indemnification, Payment and Invoicing, Risk of Loss, Taxes and Duties, Termination for Convenience, Termination for Default, Title and Ownership, Limited Warranty, Limitation of Liability, Compliance with Law and Agreement Status, Specific Statutory Requirements, Third-Party Terms of Service (TOS) and End User License Agreements (EULAs), Limitation of Obligation and Milestone Funding, Intellectual Property Rights, Stop-Work Order, Delivery, Defense Priorities and Allocation System (DPAS), System for Award Management (SAM), Joint Certification Program (JCP), Cybersecurity Requirements (CUI and CMMC), Country of Origin, Cyber Incident Reporting and Response, Prohibited Sources, Prohibition on ByteDance Covered Applications, Comptroller General Access to Records, Phased Execution and Optional Milestones, Duty-Free Entry, Membership and Good Standing, Project Process, Project Suspension, Operational Security and Public Release of Information, and Order of Precedence.

This document serves as a foundational reference for potential bidders by defining key terms and outlining the contractual framework for an Other Transaction Agreement. It clarifies the rights, responsibilities, and procedures governing the agreement, including aspects like acceptance criteria, dispute resolution, intellectual property, payment terms, cybersecurity requirements (CMMC Level 2), and termination clauses. Understanding these definitions and articles is crucial for any consortium member or potential bidder to comprehend the operational and legal aspects of participating in the AEDC Velocity Alliance and any subsequent projects or opportunities issued under this agreement.

Solicitation / RFP / RFQ

This document is a Request for Whitepapers to solicit vendors for membership in the AEDC Velocity Alliance. The Alliance is a strategic consortium initiative established under 10 U.S.C. § 4022 to accelerate the sustainment, restoration, and modernization of critical test infrastructure for next-generation national defense systems. Projects under this initiative will be competed exclusively among Alliance members. The Air Force anticipates investing multi-billion dollars in test infrastructure at AEDC through Fiscal Year 2032.

Vendors must submit a whitepaper demonstrating their capabilities and expertise. The whitepaper submission process involves several steps:

• Whitepaper Submission: In accordance with instructions, demonstrating agreement to the "Statement of Understanding."
• Government Evaluation: Based on Pass/Fail criteria including mandatory certifications and technical competency.
• Invitation to Site Visit: For successful vendors.
• Mandatory Site Visit: Attendance required at Arnold Air Force Base, TN.
• Execution of Membership Agreement: Upon successful completion of the site visit.

Mandatory certification requirements include:

• Joint Certification Program (JCP): Current certification required.
• Cybersecurity Maturity Model Certification (CMMC): Either CMMC Level 2 certified or an alternative compliance path including a NIST SP 800-171 Assessment and a CMMC Level 2 compliance roadmap with a deadline of November 2026.

Technical competency will be evaluated based on responses to specific project type questions, demonstrating past performance within the last five years.

This is an unfunded solicitation for qualification. The Government is not responsible for any costs incurred by vendors. Financial obligations begin only upon the award of a specific, funded Project-Level Agreement to an Alliance member.

• Whitepaper responses must be submitted electronically as a single, searchable PDF, not exceeding ten pages.

• Evaluation is a four-part Pass/Fail process: Mandatory Certifications, Technical Competency, Intellectual Property Rights Acknowledgement, and Innovation and Partnership Capability.

• Vendors must receive a "Pass" on all four parts to be considered for membership.

• Key deadlines for whitepaper responses are provided for multiple onboarding phases, with an anticipated Alliance live date of July 1, 2026.

• The Innovation and Partnership Capability section requires vendors to identify at least one partner company that is either a Non-Traditional Defense Contractor (NDC) or a small business, demonstrating their significant contribution to the project.

• The Request for Whitepapers notice will remain active until September 30, 2032.

• Governing documents (SOO and Base Articles) are considered "living documents" and subject to change.

• All questions must be submitted in writing via email.

Questions & Answers / Clarifications

This document provides Frequently Asked Questions (FAQs) regarding the Cybersecurity Maturity Model Certification (CMMC) Program, as of Revision 2.2. It aims to clarify requirements, processes, and policies for organizations seeking to comply with CMMC.

• CMMC Implementation Timeline: CMMC assessment requirements will begin to be incorporated into applicable procurements starting November 10, 2025. The initial 12 months will focus on self-assessments.
• NIST SP 800-171 and CMMC: NIST SP 800-171 is the federal standard for safeguarding controlled unclassified information (CUI). CMMC Level 2 assessments will verify compliance with NIST SP 800-171 Revision 2. The Department plans to incorporate Revision 3 in the future.
• Flow Down to Subcontractors: CMMC requirements will flow down to subcontractors based on the type of data (FCI or CUI) they handle.
• Assessment Frequency: Level 1 self-assessments are required annually, while Levels 2 and 3 require assessments every three years.
• Scope of CMMC: CMMC applies to nonfederal unclassified information systems that process, store, or transmit FCI or CUI. It does not apply to classified systems or environments.
• External Service Providers: Cloud Service Providers (CSPs) must meet FedRAMP Moderate baseline requirements if processing, storing, or transmitting CUI. Managed Service Providers (MSPs) and Managed Security Service Providers (MSSPs) may be assessed as part of the Organization Seeking Assessment's (OSA) evaluation, but do not require their own CMMC certification.
• Hard-copy CUI: Organizations handling only hard-copy CUI are generally not required to complete a CMMC Assessment, but must still safeguard the information. If hard-copy CUI is digitized, the information technology system used is subject to CMMC requirements.

This document clarifies key aspects of the CMMC program that bidders and contractors need to understand for future solicitations and contract performance. It details when CMMC will be required, the standards used (NIST SP 800-171), and how requirements apply to different entities, including subcontractors and external service providers. Understanding these FAQs is crucial for preparing accurate proposals and ensuring compliance.

Form / Attachment / Pricing Sheet

This document provides information regarding the Cybersecurity Maturity Model Certification (CMMC) Program, outlining its phased implementation and assessment requirements. It serves as a reference for potential bidders to understand the cybersecurity standards they may need to meet for Department of War (DoW) contracts.

• CMMC Program Overview: Explains the purpose of CMMC in assessing defense contractor cybersecurity compliance for Federal Contract Information (FCI) and Controlled Unclassified Information (CUI).
• CMMC Model Levels: Details three levels of certification (Level 1, Level 2, Level 3) with corresponding security requirements, assessment types, and affirmation requirements.
• Protected Information: Defines FCI and CUI.
• Assessment Requirements: Outlines the specific security requirements for each CMMC level, including the number of requirements and the source (e.g., FAR, NIST SP 800-171).
• Post-Assessment Remediation: Explains the use of Plans of Actions and Milestones (POA&Ms) for Levels 2 and 3.
• Phased Implementation: Describes a four-phase plan for CMMC implementation from November 2025 to November 2028, detailing when different levels of certification will be required.

Bidders should review this document to understand the cybersecurity compliance requirements that may be applicable to current and future solicitations. It details the phased rollout of CMMC, indicating when specific CMMC levels will become mandatory for contract awards. Understanding these requirements is crucial for preparing proposals and ensuring compliance.

Other / Unclassified

This document outlines the objectives and project categories for the Arnold Engineering Development Complex (AEDC) Velocity Alliance Program. The program aims to sustain and advance AEDC's flight simulation test facilities through improvement, modernization, restoration, and maintenance of critical test assets and supporting utilities. Key goals include enhancing operational readiness, integrating innovative engineering solutions, increasing system reliability, and ensuring long-term viability.

The document details various project types and their scope definitions, which are crucial for potential bidders to understand the range of work AEDC is undertaking. The categories cover a broad spectrum of construction, industrial, process systems (low and high pressure, hazardous), electrical (high, medium, low voltage), fire suppression, equipment repair, mechanical and electrical engineering services, ID&C systems, and utilities. This information helps vendors assess their capabilities and determine their interest and suitability for future opportunities within the Velocity Alliance Program.