Scope
Explain the technical requirements of your scope and how your team executed the work and integrated it with other ongoing project activities.
DEPT OF DEFENSE · DEPT OF THE AIR FORCE · FA9101 AEDC PKP PROCRMNT BR
The Department of the Air Force is establishing the AEDC Velocity Alliance, a consortium to accelerate national test infrastructure modernization for next-generation defense systems. This initiative involves a multi-billion dollar portfolio of complex engineering and construction projects. [2]
Documentation Requirement for Each POA Submission When you submit a proposal for a POA that involves flowing down sensitive information, your submission package must include the following for each applicable subcontractor: • A copy of their CMMC Level 2 Self-Assessment (or C3PAO Certification, if applicable). • A copy of their approved DD Form 2345 (Militarily Critical Technical Data Agreement).
Posted Aug 31, 2026; Responses due Sep 30, 2030, 10:00 PM UTC; Archive date Oct 15, 2030
Generated from the public notice and source-backed solicitation passages. Confirm important requirements in the cited brief and official documents.
DEPARTMENT OF THE AIR FORCE HEADQUARTERS AIR FORCE MATERIEL COMMAND WRIGHT-PATTERSON AIR FORCE BASE OHIO One AFMC…Powering the World’s Greatest Air Force 5 Mar 26 MEMORANDUM FOR AEDC VELOCITY ALLIANCE CONSORTIUM MEMBERS FROM: AFMC/AFTC/PZIA (Arnold) 100 Kindel Drive Arnold AFB, TN 37389-1332 SUBJECT: AEDC Velocity Alliance Base Articles Article Definitions As used throughout this Agreement, the following terms shall have the meanings set forth below: • Acceptance: The Government's formal, written acknowledgement that a prototype, deliverable, or milestone has been successfully demonstrated to meet the pre-defined Acceptance Criteria. • Acceptance Criteria: The specific, measurable, and testable requirements that a prototype, deliverable, or milestone must meet to be accepted by the Government, as detailed in the Acceptance Test Plan or Statement of Work. • Agreement: This Other Transaction (OT) Agreement, executed under the authority of 10 U.S.C. § 4022, including all attachments and subsequent modifications. • Agreements Officer (AO): The Government official with the authority to enter into, administer, and modify this Other Transaction Agreement on behalf of the Government. • Consequential Damages: Indirect, special, incidental, or punitive damages, including but not limited to, lost profits, loss of use, loss of revenue, or loss of data. • Contractor / Performer/ Vendor: The non-government party to this Agreement. • Controlled Unclassified Information (CUI): Information the Government creates or possesses, or that an entity creates or possesses for or on behalf of the Government, that a law, regulation, or Government-wide policy requires or permits an agency to handle using safeguarding or dissemination controls. • Cure Notice: A written notice from the non-breaching Party that details a material failure of performance and provides the breaching Party with a specified period to correct the failure. • Cyber Incident: An action taken through the use of computer networks that results in a compromise or an actual or potentially adverse effect on an information system or the Controlled Unclassified Information (CUI) residing therein. • Cybersecurity Maturity Model Certification (CMMC): The DoD's framework for verifying that a Performer has implemented the required cybersecurity standards to protect CUI. • Direct Damages: The damages that arise naturally and foreseeably from a breach of this Agreement in the usual course of events.
Explain the technical requirements of your scope and how your team executed the work and integrated it with other ongoing project activities.
The Performer shall provide the Government with a delivery schedule and necessary shipping documentation.
Is there an expected process for competition of the possible projects; will awards be based on best value or lowest price evaluations?
Documentation Requirement for Each POA Submission When you submit a proposal for a POA that involves flowing down sensitive information, your submission package must include the following for each applicable subcontractor: • A copy of their CMMC Level 2 Self-Assessment (or C3PAO Certification, if applicable). • A copy of their approved DD Form 2345 (Militarily Critical Technical Data Agreement).
Posted Aug 31, 2026; Responses due Sep 30, 2030, 10:00 PM UTC; Archive date Oct 15, 2030
Extracted from the official notice and archived solicitation files. Confirm controlling requirements in the source documents.
1. Strategic Purpose: The Department of the Air Force, through the Air Force Test Center (AFTC) and Arnold Engineering Development Complex (AEDC), announces the establishment of the AEDC Velocity Alliance. This strategic consortium-based initiative is established under the authority of 10 U.S.C. § 4022 to accelerate the modernization of national test infrastructure in direct support of next-generation defense systems and key National Defense Strategy objectives. The objective is to establish a pre-qualified industrial base to execute a multi-billion dollar portfolio of complex engineering and construction projects. Upon establishment, all projects under this initiative will be competed exclusively among Alliance members. 2. Key Dates for Industry: The Government intends to onboard members in multiple phases. Onboarding Opportunity 1: Whitepapers Due: Closed Mandatory Site Visit Window: Completed Consortium Activation Date: 1 July 2026 Onboarding Opportunity 2: Whitepapers Due: 1 September 2026, COB Mandatory Site Visit Window: 16 September 2026 (Virtual Event) This Request for Whitepaper notice will remain active until: 30 September 2032. 3. Action Required: We invite all interested and qualified vendors to carefully review the attached documents in their entirety to ensure all mandatory onboarding criteria are satisfied within their whitepaper submission. 4. Classification Codes: Primary NAICS Code: 541330 - Engineering Services: This NAICS Code will be utilized to determine size standard for consortium onboarding. Primary NAICS code at the project level may differ from 541330 and will be established in each Project Oppurtunity Announcement. Primary PSC Code: AC13 - National Defense R&D Services; Department of Defense - Military; Experimental Development (Note: While these are the primary codes, any NAICS/PSC code that fits within the scope of the Program Objectives is acceptable.) Amendments: 30 Mar 26: Posted Question and Answers received to date in document - AEDC Velocity Alliance Consortium_Q_A-3.30.26.pdf 31 Mar 26: Posted Question and Answers received to date in document - AEDC Velocity Alliance Consortium_Q_A-3.31.26.pdf 31 Mar 26: Posted Question and Answers received to date in document - AEDC Velocity Alliance Consortium_Q_A-3.31.26-2.pdf 14 Apr 26: Posted Question and Answers received to date in document - AEDC Velocity Alliance Consortium_Q_A-4.15.26.pdf Section 4: Classification Codes was modified to clarify the following: Primary NAICS Code: 541330 - Engineering Services: This NAICS Code will be utilized to determine size standard for consortium onboarding. Primary NAICS code at the project level may differ from 541330 and will be established in each Project Oppurtunity Announcement. 17 Apr 26: Posted Question and Answers received to date in document - AEDC Velocity Alliance Consortium_Q_A-4.17.26.pdf 21 Apr 26: Posted the following Amended Documents - AEDC Velocity Alliance - Request for Whitepaper-Amend 1 - 21 Apr 26.pdf Atch 1 - AEDC Velocity Alliance Program Objectives - 21 Apr 26.pdf Atch 2 - AEDC Velocity Alliance Base Articles - 21 Apr 26.pdf AEDC Velocity Alliance Consortium_Q_A-4.21.26.pdf (Answer to Q.9 Amended) 23 Apr 26: Posted Question and Answers received to date in document - AEDC Velocity Alliance Consortium_Q_A-4.23.26.pdf 24 Apr 26: Posted Question and Answers received to date in document - AEDC Velocity Alliance Consortium_Q_A-4.24.26.pdf 27 Apr 26: Posted Question and Answers received to date in document - AEDC Velocity Alliance Consortium_Q_A-4.27.26.pdf 28 Apr 26: Posted Question and Answers received to date in document - AEDC Velocity Alliance Consortium_Q_A-4.28.26.pdf 30 Apr 26: Posted Question and Answers received to date in document - AEDC Velocity Alliance Consortium_Q_A-4.30.26.pdf 1 May 26: Posted Question and Answers received to date in document - AEDC Velocity Alliance Consortium_Q_A-5.1.26.pdf 1 May 26: Posted Question and Answers received to date in document - AEDC Velocity Alliance Consortium_Q_A-5.1.26-2.pdf 12 May 26: Posted Question and Answers received to date in document - AEDC Velocity Alliance Consortium_Q_A-5.12.26.pdf 15 May 26: Posted Amendment 2, Amendment 2 summary of changes, and Atch 5-UTSI Map. This amendment establishes the date/time/location for Oppurtunity 1 Mandatory Site Visit (Industry Day) 22 May 26: Posted Question and Answers received to date in document - AEDC Velocity Alliance Consortium_Q_A-5.22.26.pdf 26 May 26: Posted Question and Answers received to date in document - AEDC Velocity Alliance Consortium_Q_A-5.26.26.pdf 14 Jun 26: Posted Question and Answers received to date in document - AEDC Velocity Alliance Consortium_Q_A-6.14.26.pdf 23 Jun 26: Posted Question and Answers received to date in document - AEDC Velocity Alliance Consortium_Q_A-6.23.26.pdf 24 Jun 26: Posted Question and Answers received to date in document - AEDC Velocity Alliance Consortium_Q_A-6.24.26.pdf 15 Jul 26: The following documents were posted to announce Oppurtunity 2 Industry Day date / location, revise CMMC Requirements, implement the use of 10 U.S.C. 2808a, provide updated Base Agreement Articles, and post Consoritum Q&As. - AEDC Velocity Alliance - Request for Whitepaper-Amend 3 - 15 Jul 26.pdf - Atch 1 - AEDC Velocity Alliance Program Objectives - 21 Apr 26.pdf - Atch 2 - AEDC Velocity Alliance Base Articles - 15 Jul 26.pdf - Atch 3 - CMMC-Information.pdf - Atch 4 - CMMC-FAQsv6.pdf - Atch 5 - AEDC Velocity Alliance Consortium_Q_A-7.15.26.pdf 17 Jul 26 - The following documents were amended: - AEDC Velocity Alliance - Request for Whitepaper-Amend 4 - 17 Jul 26.pdf, modified criteria found in 4.0 Part 1, and 5.0 Part 1 - Atch 2 - AEDC Velocity Alliance Base Articles - 17 Jul 26.pdf, Article: Cybersecurity Requirements (CUI and CMMC) was revised - AEDC Velocity Alliance Consortium_Q_A-7.17.26.pdf was posted. 26 Aug 26 - The following documents were amended: - AEDC Velocity Alliance - Request for Whitepaper-Amend 5- 26 Aug 26.pdf - Under Section 4.0, Part 2: Technical Competency, Technical Evaluation #16 was added for Solid Rocket Motors and Components - Atch 1 - AEDC Velocity Alliance Program Objectives - 26 Aug 26.pdf - Objective - Solid Rocket Motors and Componets was added 31 Aug 26: Posted Question and Answers received to date in document - AEDC Velocity Alliance Consortium_Q_A-8.31.26.pdf
Open a filename to view the saved source file. If a saved copy is not available yet, FedRoster will continue to the matching SAM.gov notice.