RFI_N00019-27-RFI-PMA228-CCA__Frequently_Asked_Questions_(FAQ).docx

Frequently Asked Questions (FAQ) Navy Collaborative Combat Aircraft (CCA) Increment 1 Prototype Project RFI Reference: N00019-27-RFI-PMA228-CCA Issuing Agency: Naval Air Systems Command (NAVAIR) / Future Advanced Capability Program Management Office (PMA-228) Consortium Partner: Naval Air Systems Consortium (NASC) / Consortium Management Group (CMG) Document Release Date: 14 September 2026 Classification: UNCLASSIFIED // Approved for Public Release

Section 1: General Scope, Teaming, & Acquisition Strategy Q1.1: Is this RFI solely focused on prime airframe manufacturers, or does the Government encourage responses from subsystem manufacturers, software providers, and mission autonomy developers?

A: The RFI is intended for industry writ large. While overall platform airworthiness and carrier suitability are core focus areas, the Government strongly encourages responses, capability statements, and technical approaches from subsystem manufacturers, software integrators, sensor providers, and mission autonomy developers. Submissions representing partial solutions or specialized subsystem capabilities are accepted; however, submission of a response does not obligate the Government to enter into an agreement.

Q1.2: How does the Government recommend non-prime vendors, component suppliers, and autonomy providers connect with prospective prime performers?

A: The Government encourages industry to utilize the Naval Air Systems Consortium (NASC) teaming mechanisms and participate in the upcoming Industry Day. Specific teaming support includes:

Industry Day Attendee Directory: Following Industry Day, an attendee directory containing participating company names and CAGE codes (with optional POC information) will be shared with registered participants to facilitate collaboration.

Capability Summaries: Industry partners wishing to explore partnering opportunities may voluntarily provide a brief capability profile (a maximum 200-character summary and/or a 3-4 sentence capability statement along with an optional technical POC) through the NASC collaboration channels.

Q1.3: What is the relationship between this RFI, the upcoming Industry Day, and future solicitations?

A: This RFI is conducted solely for information and planning purposes (market research) under 10 U.S.C. § 4022. It will be complemented by the PMA-228 Industry Day hosted through NASC. Following Industry Day, the Government plans to issue a formal Request for White Papers (RWP) containing the final Statement of Need (SON) through CMG/NASC, which may lead to subsequent prototype project awards.

Section 2: Security Classification, CUI, & Annex Access Q2.1: Page 2 of the RFI indicates that all submissions must be unclassified, whereas Section 6.2 references CUI. What is the allowable classification level for RFI responses, and will classified submissions be accepted?

A: **UPDATE** For this RFI, the Government will not entertain or accept submissions above Controlled Unclassified Information (CUI). All RFI capability statements and responses must be submitted at the CUI level or lower.

Submissions above CUI (classified responses) will be permitted under the future formal Request for White Papers (RWP) phase, for which detailed classified submission and transmission instructions will be provided. Submissions marked Distribution F will not be reviewed.

Q2.2: Will the Government provide the CUI and Classified Technical Annexes prior to the RFI response due date or at Industry Day?

A: No. The CUI and Classified Technical Annexes will not be released for the RFI submission phase or during Industry Day. These annexes will be officially released during the formal Request for White Papers (RWP) phase alongside the final Statement of Need (SON).

Q2.3: What are the eligibility and vetting requirements for industry partners to receive the CUI and Classified Annexes once released during the RWP phase?

A: To receive the CUI and/or Classified Annexes during the RWP phase, interested vendors must satisfy the following criteria:

Active membership in the Naval Air Systems Consortium (NASC).

Verification of active CAGE Code and Unique Entity Identifier (UEI).

A fully executed CUI Non-Disclosure Agreement (NDA) signed by an authorized corporate official and submitted to CMG (rwp@cmgnetworks.org).

Identification of an authorized, cleared individual recipient point of contact (POC).

Self-certification of Cybersecurity Maturity Model Certification (CMMC) Level 2 compliance and NIST SP 800-171 compliance verification for non-DoD information systems hosting CUI.

Upon completion of vetting, CMG will disseminate the CUI Annex. The Government will transmit the Classified Annex in accordance with authorized classified dissemination methods based on facility clearance level and safeguarding capabilities.

Q2.4: Is there an updated Security Classification Guide (SCG) available to reference in order to leverage prior Navy CCA work with PMA-228?

A: Specific security classification guidelines, threshold determinations, and updated SCG references will be discussed during Industry Day and provided in conjunction with the formal Request for White Papers (RWP) and Statement of Need (SON) release by CMG/NASC. Company-specific security inquiries may be directed to CMG.

Q2.5: Is new CCA design work developed exclusively to answer this RFI classified CUI or S//SAR by default?

A: Respondents should consult their internal security classification processes and baseline program security guidelines. The Government requests that responses to this RFI be submitted at the CUI level or lower. Submissions above CUI will not be entertained for this RFI.

Section 3: Technical Requirements & Operational Architecture Q3.1: Will the Government provide detailed clarifications regarding specific prototype technical parameters—such as external/internal weapons carriage configurations, weapon bring-back requirements, autonomy tier definitions (Level 1 MA vs. Level 2 skills), data transport architectures, unit cost scope, and prototype-to-production fidelity?

A: To safeguard potentially sensitive operational thresholds and Controlled Unclassified Information (CUI), granular technical specifications and design thresholds will not be addressed individually in this unclassified RFI FAQ.

Detailed operational requirements—including weapons carriage configurations and bring-back parameters, survivability expectations, Flight Autonomy (FA) and Mission Autonomy (MA) architectural definitions and boundary delineations, resilient tactical datalink architectures, target unit flyaway cost scopes, and prototype-to-production fidelity expectations—will be discussed during the upcoming Industry Day and/or fully defined in the final Statement of Need (SON) to be released in the Request for White Papers (RWP) by CMG/NASC after Industry Day.

Respondents to this RFI should base their initial capability statements on the high-level attributes published in Section 3.0 of the RFI and highlight their organization's relevant technical approaches, past performance, and architectural trade space.

Section 4: Administrative, Formatting, & Submission Guidelines Q4.1: Is an 8-point font permissible for embedded tables, graphics, diagrams, and callouts?

A: Yes. An 8-point Times New Roman (or comparable legible font) is acceptable for tables, diagrams, figures, and charts, provided all text and data remain clearly legible. Body text must remain at 10-point Times New Roman font or larger with 1-inch margins, as specified in Section 4.0.

Q4.2: What is the maximum allowable page count for RFI responses?

A: Submissions are limited to:

Capability Statement (CS): Maximum of ten (10) pages (8.5 x 11-inch paper, 1-inch margins, 10pt font or larger).

Amplifying Presentation Materials: Maximum of ten (10) pages (briefs, graphics, architectural diagrams, data flows).

Total page limit: Twenty (20) pages.

Q4.3: Where and to whom should responses be submitted?

A: Responses must be submitted electronically in Microsoft Word or searchable Adobe PDF format no later than September 18, 2026, at 5:00 PM ET to:

Contract Specialist: Emily Burgkhardt (emily.h.burghardt.civ@us.navy.mil) Procuring Contracting Officer: Raymond Cannon (raymond.c.cannon2.civ@us.navy.mil) Submissions must clearly identify the RFI reference number (N00019-27-RFI-PMA228-CCA), company name, CAGE code, UEI, corporate address, and designated technical/business POCs.