Partially reviewed: Too large

• Authority: 10 U.S.C. §4022 — consortium/OTA prototype authority (enables non‑traditional acquisition model).
• Primary NAICS: 541330 (Engineering Services); Primary PSC: AC13 (National Defense R&D Services).
• Program scale: Government anticipates multi‑billion dollar investment in AEDC infrastructure through FY2032.
• Onboarding schedule (Phase 1): Questions due 1 May 2026; Whitepapers due 1 Jun 2026; Mandatory site‑visit window 1–30 Jun 2026; Anticipated consortium live date 1 Jul 2026.
• Onboarding schedule (Phase 2): Whitepapers due 1 Sep 2026; Mandatory site‑visit window 1–30 Sep 2026; notice active through 30 Sep 2032.
• Membership process: Whitepaper submission -> Government pass/fail evaluation -> Invitation to mandatory site visit -> Mandatory site‑visit attendance -> Execution of AEDC Velocity Alliance Membership Agreement (required to be eligible to compete).
• Mandatory certifications (non‑negotiable pass/fail criteria): JCP (DD Form 2345) verification via DLA; CMMC Level 2 OR alternative path requiring current NIST SP 800‑171 DoD Assessment in SPRS (≤3 years) plus a CMMC L2 roadmap to achieve certification by 10 Nov 2026.
• Whitepaper format constraints: Part 2 Technical Competency responses limited to 10 pages and must begin with vendor legal name and CAGE code.
• Breadth of technical scope requested: explicit line items include general/industrial construction; low/high pressure process systems; hazardous process systems; large process ducting; high/medium/low voltage electrical; fire suppression; equipment repair; mechanical, electrical, and ID&C engineering; utilities — indicating heavy engineering/construction and specialized systems work.
• Place(s) of performance called out: Arnold AFB (TN), Holloman AFB (NM), Tunnel 9 (Silver Spring, MD), NFAC (Moffett Field, CA) (and ‘may include but not limited to’ other AFTC sites).
• IP baseline: Government’s default position is unlimited Government use rights for all aspects of delivered prototypes; whitepaper must include explicit acknowledgement of that baseline.
• Innovation/partnering requirement: Vendors must identify at least one named partner (with CAGE) that enables compliance with either (A) a nontraditional defense contractor or nonprofit research institution participating to a “significant extent,” or (B) that all significant participants other than the government are small businesses — submission must demonstrate partner’s role and relationship.
• Evaluation style: Whitepapers evaluated on pass/fail criteria (document references a separate 'Whitepaper Evaluation Criteria'); successful pass required prior to site visit invitation.
• Whitepaper constitutes agreement to terms in the 'Statement of Understanding' (submission implications).

• Government will manage the consortium internally (no industry-run consortium manager).
• Membership requires each prospective member to demonstrate an established relationship with one of: a Non-Traditional Defense Contractor (NDC), a Small Business, or a Nonprofit Research Institution (per 10 U.S.C. §4022(d)(1)(A) or (B)).
• Whitepapers should identify the partner by name and CAGE code and be prepared to confirm 501(c)(3) or equivalent status for nonprofit research institutions.
• Guidance: feature a university partner in "Part 4" and link partner capabilities directly to technical project described in "Part 2"—partner must be able to participate to a "significant extent."
• Standalone paving work can be competed within the Alliance by leveraging the existing "General Construction" category (implies construction scope can be included under certain categories).
• Document authored/signed by Greggory C. Jones, Agreements Officer, USAF (point of authority for the Q&A).

• Document is AEDC Program Objectives for Arnold Air Force Base, Tennessee (Distribution A: public release).
• Primary mission: sustain/modernize flight simulation test facilities and supporting utilities.
• Project categories cover both construction (general, industrial) and complex engineering domains (mechanical, electrical, ID&C).
• Lifecycle expectation: analysis, planning/design, procurement, fabrication/installation or demolition, and verification & validation across categories.
• Process systems: low pressure (<=150 PSIG) and high pressure (>150 PSIG) distinctions; hazardous process systems require OSHA-level safety focus.
• Process ducting defined for >24 inch diameter ducting (non-ASHRAE); indicates large-scale HVAC/airflow work.
• Electrical scope split by voltage: Low (<=600V), Medium (600V–6.9kV), High (>6.9kV) with associated distribution, switchgear, transformers, and motor control needs.
• ID&C (Instrumentation, Data, & Control) explicitly includes sensors, controllers, HMI/software development, and system verification.
• Fire suppression and equipment repair (motors, pumps, cranes) included as discrete lifecycle categories.
• Utilities work includes raw water and steam distribution systems — indicates civil/utility engineering and infrastructure upgrades.

Partially reviewed: Too large

• Agreement vehicle: Other Transaction executed under 10 U.S.C. §4022 — explicitly not a FAR-based procurement.
• Acceptance model: Defined acceptance criteria tied to three prototype types (Business Process, Proof of Concept, Operational Utility); no separate acceptance test plan required.
• Demonstration process: Vendor notifies AO when deliverables complete; Government verifies against Key Elements for Success; formal written acceptance required.
• Latent defects: Performer remains responsible for latent defects after acceptance, subject to Government notice conditions.
• Funding constraints: Agreement may be incrementally funded; Government liability limited to funds allotted; Performer must notify AO ≥60 days before anticipated >80% spend of allotted funds.
• Statutory compliance: Performer must comply with 31 U.S.C. §1352 (lobbying restrictions) as made applicable to the OT.
• IP allocation principles: Government receives Unlimited Rights for tech developed exclusively with Government funds; Government Purpose Rights for mixed funding; Limited/Restricted Rights for private-only development (background IP).
• Third-party TOS/EULAs: Government cannot be bound to unenforceable commercial EULA/TOS clauses (indemnities, open-ended obligations); click-wrap acceptance by users cannot bind the Government to such provisions.
• Modification & payments: Changes require bilateral written modification; Performer may assign payment rights to financial institutions except where payment is from a third party.
• Dispute resolution: Collaborative dispute resolution process required; escalation timeline (15 business days to senior-level, 30 business days for written response); Contract Disputes Act does not apply; litigation limited to U.S. federal courts; ADR permitted.
• Cyber/CUI controls: Definitions and references to CUI and CMMC appear, signaling cybersecurity requirements for handling controlled information.

• Source: DoD CIO CMMC guidance (applicable to DoD solicitations).
• CMMC Levels: Level 1 (15 FAR 52.204-21 controls; annual self‑assessment/affirmation), Level 2 (110 NIST SP 800‑171 R2 controls; self‑assessment or C3PAO every 3 years plus annual affirmation), Level 3 (Level 2 plus 24 NIST SP 800‑172 controls; assessed every 3 years by DIBCAC).
• Assessment authorities: Level 1 by organization seeking assessment (self); Level 2 by self or authorized C3PAO; Level 3 by DIBCAC (DCMA).
• Reporting and systems: Results and affirmations entered into SPRS and CMMC eMASS as applicable; POA&Ms entered and tracked per guidance.
• POA&M constraints: POA&Ms limited; POA&M closeout must be completed within 180 days or Conditional CMMC Status expires; different closeout assessment rules for Levels 2 and 3 (C3PAO/DIBCAC).
• Implementation phases and dates: phased plan over 3 years; Phase 2 begins 10 Nov 2025, Phase 3 begins 10 Nov 2026, Phase 4 begins 10 Nov 2028; DoD may require Level 2 (C3PAO) in some Phase 1 procurements or Level 3 in some Phase 2 procurements (i.e., solicitations may impose higher CMMC earlier).
• Contract implications: CMMC status can be a condition of contract award or option periods—failure to maintain affirmations can cause assessment lapse and affect eligibility.
• Referenced regulations and clauses: DFARS 252.204-7012, FAR 52.204-21, 32 CFR part 170 (CMMC rule).

Partially reviewed: Too large

• Document: CMMC Frequently Asked Questions, Revision 2.2, January 2026 (partial extraction).
• Effective date: Department began incorporating CMMC assessment requirements on November 10, 2025; initial 12 months emphasize self-assessments.
• Assessment requirement: Beginning Nov 10, 2025, applicable contractors must undergo a Level 2 self-assessment or a CMMC third-party assessment to verify NIST SP 800-171 Rev2 compliance.
• Assessment frequency: Level 1 self-assessments annually; CMMC Levels 2 and 3 every 3 years; annual affirmation of continued compliance required.
• Baseline standard: NIST SP 800-171 Revision 2 is the assessment baseline until Revision 3 is incorporated via rulemaking (class deviation keeps Rev2 as current standard).
• Flow-down: CMMC requirements flow down to subcontractors; when prime requires Level 3, subcontractors must meet at least Level 2 unless Government specifies otherwise.
• Cloud guidance: CSPs processing/storing/transmitting CUI should meet FedRAMP Moderate; MSP/ESP handling CUI may need their own assessment depending on role.
• Visibility/verification: Assessment results are not publicly listed; the Department can access results; suppliers can share SPRS verification with primes or teammates.
• Resources: Points vendors to Cyber AB marketplace, Defense Acquisition University training, and DoD DIB CSaaS resources for compliance assistance.
• Relevance to solicitation: Engineering services (NAICS 541330) bidders will likely need to demonstrate appropriate CMMC/NIST compliance per this guidance.