Indefinite Delivery Indefinite Quantity Contract for Inland and Coastal Vessels Engineering Services, Naval Architecture, and Marine Engineering
Department of the Army
Why this score
Small-business set-aside, active buyer ($19.9B FY24–FY26).
Solicitation # FA9101-26-9-Velocity_AllianceUpdated Nov 15, 2026Scored Nov 18, 2026
Amended Nov 16, 2026: Description updated
Sep 30
Sep 30, 2030, 5:00 PM CDT
Summary by RFP Detector
Department of the Air Force (FA9101 AEDC PKP PROCRMNT BR), part of the Department of Defense, posted a solicitation titled “Request for Whitepapers: AEDC Velocity Alliance - A Multi-Billion Dollar OTA Consortium Opportunity” under solicitation number FA9101-26-9-Velocity_Alliance. It was first posted on Mar 17, 2026 and has been updated 29 times since. Responses are due Sep 30, 2030, 5:00 PM CDT. It is classified under NAICS 541330 (Engineering Services) and product/service code AC13. No set-aside is listed. The listed point of contact is Greggory Jones.
RFP Detector Score
Every RFP starts at 50. Each factor adds or subtracts points compared with a typical RFP; unknown data counts as neutral.
Starts at 50
No value published. Typical award is about $600K: the median of 2,513 Air Force contracts over $25K awarded in NAICS 541330, FY24–FY26.
Full and open competition. The largest recipient took 5% of these dollars in FY24–FY26, and spending is spread across many vendors.
Air Force obligated $22.8B on NAICS 541330 across 2,718 contracts in FY24–FY26. 20 other notices from this office in the past 12 months.
Solicitation, bids due: 1413 days to respond (due Sep 30, 2030, 5:00 PM CDT). Long lead time.
Documents not listed, 2 named contacts with email, 1,304-word description.
Updated 2 days ago (scope change).
50 + contributions = 81 (A, Excellent)
Informational, not advice to bid or not bid. Score version 1.0.0, evaluated Nov 18, 2026.
Eligibility · Full and open competition
Full and open competition means the notice states no set-aside: any responsible business can respond, subject to the requirements in the notice.
Not stated in a form we could extract. See the official solicitation for requirements, evaluation criteria and submission steps.
From the official notice
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: Closed Mandatory Site Visit Window: Complete Onboarding Opportunity 3: Whitepapers Due: 24 February 2027, 10:00AM CST Mandatory Site Visit Window: 28 April 2027 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 15 Oct 26: AEDC Velocity Alliance - Request for Whitepaper-Amend 6- 15 Oct 26.pdf posted and will be the basis for evaluating onboarding 3 whitepapers. Atch 2 - AEDC Velocity Alliance Base Articles - 15 Oct 26.pdf was updated by adding the Performer Representation article. 15 Oct 26 - AEDC Velocity Alliance - Request for Whitepaper-Amend 7- 15 Nov 26.pdf posted and will be the basis for evaluting onboard 3 whitepapers. Atch 2 - AEDC Velocity Alliance Base Articles - 15 Nov 26.pdf was updated & Atch 6 - VAC_RWP_Part_4_Identified_Partner_Self_Certification.pdf was incorprated. AEDC Velocity Alliance Consortium_Q_A-11.15.26.pdf: Amendment 7 — Summary of Principal Changes Adds two new Base Articles Inaccurate 10 U.S.C. § 4022(d) Self-Certification: Establishes that § 4022(d) certifications and supporting information are material; requires prompt notice of material inaccuracies; addresses pre-award and post-award consequences; preserves Government recovery/setoff rights to the extent permitted by law; and applies the existing Termination for Default and Termination for Convenience articles rather than creating a separate termination remedy. Organizational Conflicts of Interest and Competition Integrity: Establishes requirement-specific OCI disclosure, review, mitigation, and eligibility procedures to protect against biased ground rules, unequal access to nonpublic information, impaired objectivity, and other competitive-integrity concerns. Establishes the Opportunity 3 onboarding schedule Whitepaper submission deadline: 24 February 2027 Mandatory Industry Day: 28 April 2027 Opportunity 1 and Opportunity 2 are closed/completed. Revises how 10 U.S.C. § 4022(d) partnership capability is evaluated at membership entry The Prime Vendor, not the partner, must complete and sign a separate Attachment 6 self-certification for each identified partner. The Prime Vendor bears responsibility for the asserted partner’s identity, eligibility status, existing relationship, anticipated role, unique capability, and significant-extent rationale. This is a membership-entry assessment only. It does not establish a project-specific appropriate-use finding, bind the partner to participate, or replace the separate § 4022(d) analysis, self-certification, and supporting documentation required for each future POA or PLA. For this RFWP Part 4 assessment, the Prime Vendor may rely only on prospective applicability of Conditions A or B; Condition C cost share and Condition D exceptional circumstances are not available for satisfying the Part 4 requirement.
No documents are listed for this notice.
Greggory Jones
PrimaryBailey Deason
Points of contact as published on the notice.
1 change since posting.
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Solicitation posted
Description updated
Responses dueNext · in 1412 days
Archive date on the official notice
Federal award history
Department of the Air Force · NAICS 541330 · FY24–FY26
Recipients of past awards in this market, not the incumbent of this RFP.
| Fiscal year | Obligated ($) |
|---|---|
| FY2022 | 6,998,994,051.14 |
| FY2023 | 7,823,204,549.67 |
| FY2024 | 8,391,364,897.18 |
| FY2025 | 8,271,692,578.24 |
| FY2026 | 6,169,995,292.66 |
Federal contract award records, award types A–D, FY24–FY26. Updated Nov 13, 2026.
Same NAICS group or Engineering & Architecture, nearby first, ranked by score.
Department of the Army
Why this score
Small-business set-aside, active buyer ($19.9B FY24–FY26).
Department of the Army · New Orleans, LA
Why this score
Active buyer ($19.9B FY24–FY26), partial small-business set-aside.
Department of Veterans Affairs · Kansas City
Why this score
EDWOSB set-aside, new this week.
Department of the Navy · Maryland
Why this score
Active buyer ($68B FY24–FY26), 27 days to respond.
Department of the Navy
Why this score
Active buyer ($68B FY24–FY26), 31 days to respond; but limited documentation.
Department of the Air Force · Eielson AFB, AK
Why this score
Small-business set-aside, 23 days to respond.
RFP Detector Scores are informational.How we score →
720 open RFPs from this issuer and its offices.
Department of the Air Force · Spangdahlem
Why this score
Clear, complete notice; but only less than a day left.
Department of the Air Force · Yigo, GU
Why this score
Small-business set-aside, recently updated; but only less than a day left.
Department of the Air Force · Saint Louis, MO
Why this score
New this week; but only less than a day left.
Department of the Air Force · Warner Robins, GA
Why this score
But only less than a day left.
Department of the Air Force · Wright Patterson AFB, OH
Why this score
Active buyer ($6B FY24–FY26); but only less than a day left.
Department of the Air Force · Goodfellow AFB, TX
Why this score
Small-business set-aside, recently updated; but only less than a day left.
RFP Detector Scores are informational.How we score →
Official federal notice. Updated Nov 15, 2026.
Official solicitation:Sign in free to open the official solicitation
RFP Detector is an independent service and is not affiliated with any government agency. Scores are informational.
RFP Detector is not affiliated with the organization that issued this RFP. Always rely on the official notice and confirm every date and requirement with the issuer.