CALL for INNATE 08 AUG 2023 and Attachments.pdf

FA2391-23-S-2403

Pioneering Aerospace Capabilities, Engineering and Research

(PACER)

Innovative Architecture and Technology (INNATE) CALL

OVERVIEW INFORMATION

NAICS Code: The NAICS Code for this acquisition is 541715 (Research and Development in the Physical, Engineering, and Life Sciences (Except Biotechnology) with Aircraft, Aircraft Engine, and Engine Parts exception), and the small business size standard is 1,500 employees.

Federal Agency Name: Air Force Research Laboratory, Aerospace Systems Directorate, AFRL/RQT

Broad Agency Announcement Type: This is Innovative Architecture and Technology (INNATE) Call against the initial FA2391-23-S-2403. This is a two step call. The first step is a Call for White Papers.

Moratorium on White Papers: Beginning from the date of publication of this call and continuing until six months after the due date for proposals, no white papers submitted covering the topic specified in this call, “RQT Topic 14 – Future Enabling Air Breathing Propulsion” will be reviewed.

Broad Agency Announcement Number: FA2391-23-S-2403

DUE DATE AND TIME: White Paper Due Date and Time: 22 Sep 2023 local time 4:00 P.M. Wright-Patterson AFB, OH. NOTE: Proposal receipt after the due date and time shall be governed by the provisions of FAR 52.215-1(c)(3). Early proposal submission is encouraged.

Submission: White Paper Proposals must be submitted to the Primary Contracting Point of Contact (POC): Peter Seiley, Contracting Officer, AFRL/RQKPB, Bldg 45, 2130 8th St., Wright-Patterson AFB, OH 45433-7541. Submission will be electronic.

Proposals can be submitted by email to Peter.Seiley@us.af.mil or offerors may request a DOD Safe Drop Off Request by email to Peter.Seiley@us.af.mil at least 4 calendar days prior to White Paper due date.

Type of Contract/Instrument: The Air Force reserves the right to award the instrument best suited to the nature of research proposed. Accordingly, the Government may award any appropriate contract type under the FAR. The Air Force may also consider award of an appropriate technology transfer mechanism if applicable. It is anticipated that awards under this Call will be a “C” type contract with Cost Plus Fixed Fee (CPFF) CLINs anticipated.

Estimated Program Cost: The estimated total program cost is $4,800,000. This amount is estimated to cover all awards made under this call and is not the amount estimated to be awarded per contract award. As a notional example, the funding profile is split between two potential awards at a notional value of $2,400,000 each.

The funding available per year is representative of AFRL estimates of fund availability.

Anticipated Number of Awards: The Air Force anticipates two or more for this announcement. However, the Air Force reserves the right to award zero, one, or more contracts for all, some or none of the solicited efforts based on the offeror’s ability to perform desired work and funding fluctuations.

Brief Program Summary:

The objective of this effort is to conduct rapid vision system studies to discover, assess, and deliver novel propulsion architectures and technologies, which offer new capabilities and meaningfully reduces the turbine engine development timeline.

Studies conducted under this effort shall integrate relevant digital engineering and model-based system engineering methods to deliver increased system capability and shorten the conceptual engine design and vehicle integration process.

To the extent practical, capability assessments, vehicle concepts, system definitions, and digital engineering methods are to be based on leveraging existing information from prior efforts. This effort includes identification, development, and, if appropriate, but not required, proof-of-concept demonstration of applicable technology concepts relevant to the 2030+ timeframe. The technology focus may include capabilities within autonomous collaboration, high-speed platforms and weapons, rapidly produced and upgraded platforms, and other high-risk, high-payoff capability-informed concepts. Engine architectures and technologies that show the highest payoff in terms of military utility and cost effectiveness will be prioritized.

Communication Between Prospective Offerors and Government Representatives: All communication prior to the proposal deadline shall be directed to the Contracting POCs listed below.

Contracting POCs:

Peter Seiley

AFRL/RQKPB

2130 8th Street, Bldg 45 Wright-Patterson AFB OH 45433 Tel: 937-713-9943 E-mail address: Peter.Seiley@us.af.mil

FULL TEXT ANNOUNCEMENT

I. Program Description: Air Force Research Laboratory, AFRL/RQ, is soliciting white papers on the following research effort:

a. Statement of Objectives:

See Attch 1 for the contract Statement of Objectives. This effort falls within the Statement of Objectives on the PACER BAA (FA2391-23-S-2403), RQT Topic 14

– Future Enabling Air Breathing Propulsion

RQT Topic 14 – Future Enabling Air Breathing Propulsion: Research, development, demonstration, and validation of technologies or approaches that will enhance the capability, performance, endurance, and reliability of advanced air breathing propulsion for military applications.

This could include, but is not limited to, high payoff engine concepts and components with novel architectures, integrated thermal management, advanced design tools with mission-specific Multi-Disciplinary Analysis and Optimization (MDAO) and Model-Based Systems Engineering (MBSE) tools for Digital Engineering, and concepts tailored to enable effectiveness for crewed and uncrewed weapons systems.

b. Deliverable Items:

1) Data Items:

CDRL Requirements:

A001 Scientific and Technical Reports, Final Report (One-time) A002 Funds and Man-Hour Expenditure Reports (Monthly) A003 Contractor Spend and Expenditure Plan (Monthly) A004 Contract Funds Status Report (Quarterly) A005 Status Report (Quarterly) A006 Presentation Material (As requested) A007 Test Plan (As Requested) A008 Technical Data Package (As generated) A009 Scientific and Technical Reports, Interim Report (As generated) A010 Test / Inspection Report (As requested) A011 System Safety Hazard Analysis Report (As requested) A012 Detailed Research Plan (Once – 60 DACA, RASR) A013 Digital Imaging (As generated) A014 Operations Security (OPSEC) Plan (One-time) A015 Conceptual Design Drawings and Associated Lists (As generated)

A016 Developmental Design Drawings and Associated Lists (As generated) A017 Gas Turbine Engine Steady State and Transient (As generated) A018 Acquisition and Sustainment Data Package (ASDP) (Annually) A019 Technical Information Report, SF 424 Annual Update (Annually)

2) Software: No specific Software requirements exist. Software may be proposed per White Paper Proposal.

3) Hardware: No specific Hardware requirements exist. Hardware may be proposed per White Paper Proposal.

c. Schedule Contract: The contract period of performance will be 33 months, with 30 months for the technical period and 3 months for delivery of the final report.

d. Other Requirements:

1) Program Security Classification: Up to Secret (per award) See attachment

2 (DD254)

2) OPSEC: Operations Security (OPSEC) requirements, per the PACER BAA, FA2391-23-S-2403, I. (Page 9), will be incorporated into the Statements of Work.

3) Export Control: Information involved in this research effort is subject to Export Control (International Traffic in Arms Regulation (ITAR) 22 CFR 120-131, or Export Administration Regulations (EAR) 15 CFR 710-774). A Certified DD Form 2345, Militarily Critical Technical Data Agreement, is required to be submitted with the white paper.

4) Export-Controlled Items: As prescribed by DFARS 225.7901-4, DFARS 252.225-7048, “Export-Controlled Items (JUN 2013)” shall be contained in ALL resulting contracts.

e. Other Information

1) Government Furnished Property (GFP): None anticipated. If required must be identified in white paper.

2) Base Support/Network Access: None anticipated. If required must be identified in white paper.

3) Government Furnished Information (GFI) and/or Software: None anticipated. If required must be identified in white paper.

4) Data Rights: Unlimited desired. Other than unlimited rights must be identified in the white paper.

II. Award Information

a. Anticipated Award Date: Anticipated contract award date is approximately

Nov-Dec 2023.

b. Anticipated Funding: A contract type with Cost Reimbursement CLINs is anticipated in accordance with the anticipated funding set forth below.

The budget for the program, subject to availability, is anticipated to be as follows:

Notional Funding:

FY24($M) FY25($M) FY26 ($M) Total ($M)

TO #1 0.5 1.0 0.9 2.4

TO #2 0.5 1.0 0.9 2.4

III. Proposal Submission Information

a. White Paper Proposals

1) First Step: The offeror shall submit a white paper as follows.

2) Page Limitations: Page Limitation: The White Paper shall be limited to 5 pages, prepared and submitted in Word format. Font shall be standard 10-point business font Arial. Character spacing must be “normal,” not condensed in any manner. Pages shall be double-spaced (must use standard double-space function in Microsoft Word), 8.5 by 11 inches, with at least one-inch margins on both sides, top and bottom. All text, including text in tables and charts, must adhere to all font size and line spacing requirements listed herein. Font and line spacing requirements do not have to be followed for illustrations, flowcharts, drawings, diagrams, cover page, table of contents, and restrictive/proprietary markings (in header or footer). These exceptions shall not be used to circumvent formatting requirements and page count limitations by including lengthy narratives in such items. Pages shall be numbered starting with the cover page being Page 1, and the last page being no greater than Page 5. The page limitation covers all information including indices, photographs, foldouts (counted as 1 page for each 8.5 by 11 portion) tables, charts, appendices, attachments, resumes, etc. The Government will not consider pages in excess of these limitations.

3) Format: The white paper will be formatted as follows:

1) Section A: BAA Number, Title of Program, Topic Number, Name of Company, Business Size, Company’s Commercial and Government Entity

(CAGE) number, Dun & Bradstreet (D&B) Data Universal Numbering System (DUNS) number, Unique Entity Identifier (UEI) number, Contracting POC and Technical POCs with appropriate telephone numbers, and email addresses for the POCs. For submissions that will result in classified work, add the following information: Classified level at which company is cleared, contractor address for forwarding classified material (name, address, zip code), cognizant security office (name, address, zip code), and offeror’s security officer’s name and telephone number).

2) Section B: Period of Performance and Task Objectives;

3) Section C: Technical Summary and Proposed Deliverables; and

4) Section D: Cost of Task (Rough Order of Magnitude (ROM))

4) Technical Portion: The technical portion of the white paper shall include a discussion of the nature and scope of the research and the offeror’s proposed technical approach/solution. It may also include any proposed deliverables. Resumes, descriptions of facilities and equipment, and a proposed Statement of Work are not required at this point.

5) Cost Portion: The cost portion of the white paper shall include a ROM cost estimate. No detailed price or cost support information should be included;

only a time-phased bottom line figure should be provided.

6) Other Information: Multiple white papers within the purview of this announcement may be submitted by each offeror. If the offeror wishes to restrict its white papers, they must be marked with the restrictive language stated in FAR 52.215-1(e).

7) White Paper/Proposal Content Summary: You may be ineligible for award if all requirements of this solicitation are not met on the proposal due date.

b. Review and Selection Process:

1) White Paper Review Criteria (First Step):

The Government will review White Papers to determine which of them have the potential to best meet the Air Force’s needs based on the following criteria that are of descending order of importance:

1) Unique and innovative approach proposed to accomplish the technical objectives. New and creative solutions and/or advances in knowledge, understanding, technology, and the state of the art.

2) The offeror’s understanding of the scope of the technical effort.

3) Soundness of the offeror’s technical approach.

4) Affordability (Proposed ROM Cost Estimate).

2) Those offerors submitting white papers assessed as meeting Air Force needs will be asked to submit a technical proposal (second step).

3) Offerors not selected to proceed to the second step will be notified of the disposition of their white paper.

c. Second Step – Proposal Submission:

1) The SECOND STEP consists of offerors submitting a technical and busines/cost proposal within 30 calendar days of an RFP (or longer period as specified in the RFP). After receipt, proposals will be evaluated in accordance with the award criteria below. Proposals will be categorized and subsequently selected for negotiations.

2) SECOND STEP - Proposal Peer or Scientific Review Criteria: Proposals will be reviewed against the criteria listed below. The technical aspect, which is ranked as the first order of priority, shall be reviewed based on the following criteria that are of descending order of importance:

a) Technical:

(1) Unique and innovative approach proposed to accomplish the technical objectives. New and creative solutions and/or advances in knowledge, understanding, technology, and the state of the art.

(2) The offeror’s understanding of the scope of the technical effort.

(3) Soundness of the offeror’s technical approach including whether the proposal identifies major technical risks, clearly defines feasible mitigation efforts, and demonstrates related experience and qualifications of technical personnel.

(4) The potential to transition the research and development deliverables to future Government needs. Any proposed restriction on technical data or computer software will be considered.

b) Cost/Price: The cost evaluation includes the realism of the proposed cost. Cost/Price is a substantial factor, but ranked as the second order of priority. (If an offeror proposes the use of GFP other than any GFP identified in this BAA, and that proposed GFP provides the offeror an unfair competitive advantage, then FAR 45.202 requires rental equivalent be applied to the Cost Factor for evaluation purposes only).

3) Second Step Selection Categories: Based on the Peer or Scientific Review, proposals will be categorized as Selectable or Not Selectable (see definitions below). The selection of one or more sources for award will be based on the Peer or Scientific Review, as well as importance to agency programs and funding availability.

(1) Selectable: Proposals are recommended for acceptance if sufficient funding is available.

(2) Not Selectable: Even if sufficient funding existed, the proposal should not be funded.

4) Note: The Government reserves the right to award some, all, or none of the proposals. When the Government elects to award only a part of a proposal, the selected part may be categorized Selectable, though the proposal as a whole may not merit such a categorization.

5) No other criteria will be used.

6) Prior to award of a potentially successful offer, the Contracting Officer will make a determination regarding price reasonableness.

7) Additional terms, conditions, and instructions applicable to the Second

Step RFP will be sent with the Second Step RFP.

8) Section K: A completed Section K will be required to be completed with the proposal requested in the second step.

9) Model Contract: The BAA contains a model contract as an example only.

Appplicable Clauses, terms, and conditions may vary per contractor and per proposal and will be addressed during potential negotiations.

IV. Other Information

a. BAA terms, conditions, and instructions: All BAA terms, conditions, and instructions contained in BAA FA2391-23-S-2403 shall be considered applicable to this Call and white papers/second step proposals shall be in accordance with the BAA, unless deviations are authorized in this call.

b. Availability of Funds: Funds are not presently available for this contract.

The Government’s obligation under this contract is contingent upon the availability of appropriated funds from which payment for contract purposes can be made. No legal liability on the part of the Government for any payment may arise until funds are made available to the Contracting Officer for this contract and until the Contractor receives notice of such availability, to be confirmed in writing by the Contracting Officer.

c. Call White Paper/Proposal Reminders: You may be ineligible for award if all requirements of this solicitation are not met on the proposal due date.

1) Call White Papers/Proposals are due no later than the due date and time specified in the call.

2) Page limitations are strictly enforced.

3) Call White Papers/Proposals must be submitted in the format specified.

Attachments:

1. Statement of Objectives

2. Draft DD254

3. Draft CDRLs

Innovative Architectures and Technology (INNATE) CALL

Rapid Model Based System Engineering (MBSE) Novel / Modified Off-the-Shelf (OTS) Architectures & Technologies

Statement of Objectives (SOO) dated 07 July 2023

BACKGROUND:

Aspiring nation-state competitors are challenging the Air Force’s ability to project power and protect U.S. interests. Addressing these emerging threats requires scientific and technological advancements to enable the Department of the Air Force’s operational imperatives. Delivering these critical operational capabilities requires rapid development of innovative aircraft propulsion and power architectures and technologies. It is envisioned aircraft propulsion and power concepts could involve novel approaches to deliver revolutionary capability and/or require modifying existing component designs to enable rapid development.

1.0 OBJECTIVES:

The objective of this effort is to conduct rapid vision system studies to discover, assess, and deliver novel propulsion architectures and technologies, which offer new capabilities and meaningfully reduces the turbine engine development timeline. Studies conducted under this effort shall integrate relevant digital engineering and model-based system engineering methods to deliver increased system capability and shorten the conceptual engine design and vehicle integration process.

To the extent practical, capability assessments, vehicle concepts, system definitions, and digital engineering methods are to be based on leveraging existing information from prior efforts. This effort includes identification, development, and, if appropriate, but not required, proof-of-concept demonstration of applicable technology concepts relevant to the 2030+ timeframe. The technology focus may include capabilities within autonomous collaboration, high-speed platforms and weapons, rapidly produced and upgraded platforms, and other high-risk, high-payoff capability-informed concepts. Engine architectures and technologies that show the highest payoff in terms of military utility and cost effectiveness will be prioritized.

2.0 APPLICABLE DOCUMENTS:

2.1 Air Breathing Turbine Engine Aircraft and Missile Propulsion Security Classification Guide (SCG), dated 6 Jan 97, revised 5 Nov 20, or current version.

2.2 High Speed Technology Development Security Classification Guide (SCG) dated 8 Mar 2021.

2.3 Technology Demonstrator Systems Engineering Best Practice revised 24 Jan 18.

2.4 Test Planning Best Practice dated 1 Oct 17.

The below section 3 tasks are to be completed and priced separately (per task), including paragraphs 4, 5, 6, 7, 8, and 9:

3.0 TASKS:

3.1 Capability Assessment:

The contractor shall deliver an operational capability assessment of the proposed innovative architectures and technology that can meet DAF Operational Imperatives. Conceptual designs of air vehicle propulsion & power architectures and technologies can include novel non-conventional engine cycles, innovative application of off-the-shelf engine components, and/or advanced engine technology designs adapted to accelerate the propulsion development cycle. Provide documentation of the proposed innovative architectures and technologies that summarizes the new concept capability, key technologies, rapid capability development schedule, cost implications, and risk assessment to justify further development. The government is interested in propulsion research concepts that can be developed and demonstrated in less than four years and the associated architectures and technologies to support this objective. (CDRLs A001, A005, A006, A008, A009, A012, A013, A015, A017, A018)

3.2 Integrated Conceptual Design Process:

The contractor shall identify and integrate relevant digital engineering methods identified in the detailed research plan to shorten the conceptual engine design and vehicle integration time and reduce opportunities for error. This may involve the improved integration of engine and vehicle design processes and contractor teams using Model Based System Engineering (MBSE) and Multidisciplinary Design Analysis and Optimization (MDAO). Section 9.0 Digital System Engineering outlines additional details on potential digital engineering tasks and deliverables that may be scoped to the appropriate level of effort. (CDRLs A001, A005, A006, A008, A009, A012, A013, A015, A017, A018)

3.3 Innovative Conceptual Design Demonstration & Validation:

The contractor shall apply the digital engineering-based engine vehicle conceptual design process from 3.2 to discover engine concepts that increase system capability. The contractor shall demonstrate the engine conceptual design and vehicle integration and assessment time savings of applying digital engineering-based processes from 3.2 that meet the proposed Technical Performance Measure (TPM) objective criteria. The contractor shall include a TPM demonstration plan in the detailed research plan. The contractor shall deliver the conceptual design, models, and data generated in this effort to support future government studies and research. (CDRLs A001, A005, A006, A008, A009, A010, A012, A013, A015, A017, A018)

3.4 Proof of Concept Demonstration:

The contractor may conduct, if appropriate, but not required, feasibility testing and demonstration of relevant propulsion & power technologies identified in 3.1 that enables new architectures and/or reduces the turbine engine development timeline.

Design, fabricate, and conduct rig testing to verify performance / integration of innovative propulsion architectures and technologies up to TRL 5 & MRL 5. (CDRLs A001, A005, A006, A007, A008, A009, A010, A011, A012, A013, A015, A016, A017, A018)

3.5 Program Management & Technical Reporting:

Track technical, schedule, and cost performance; provide status reports; perform customer coordination; conduct a kickoff meeting, provide monthly progress updates, milestone/annual technical reviews; create detailed research plans and review annually; and conduct customer reviews. Quarterly technical and cost-reporting status reports will be submitted. Compile interim and final reports summarizing the effort and results. (CDRLs A001, A002, A003, A004, A005, A006, A009, A012, A013)

4.0 ENVIRONMENTAL PROTECTION:

The contractor shall assess the environmental consequences of the technology being developed from the standpoint of the project itself and from the standpoint of future scale-up for larger quantity production. If the technology has adverse environmental effects, the contractor shall develop suggestions for making the technology environmentally acceptable and indicate what impact the suggestions will have on the technology from an economic standpoint. The contractor shall document the findings. (CDRLs A001)

5.0 RELIABILITY, MAINTAINABILITY & SUPPORTABILITY (RM&S):

The contractor shall consider RM&S during the execution of this program. These considerations shall be based on engineering judgment, experience, and available data.

No separate reliability testing program shall be conducted as part of this program.

However, RM&S data shall be documented, and shortcomings reported for consideration during future developments. Supportability considerations should be addressed at levels consistent with Applied Research (6.2) and Advanced Development (6.3) activities. The contractor shall document the findings. (CDRLs A001)

6.0 SYSTEM SAFETY:

As applicable, the contractor shall identify and document any safety hazards introduced during design, fabrication, and testing. The design goal shall be to eliminate all hazards.

Any residual hazards and subsequent design risk shall be summarized and provide enough detail to support an informed program management decision about the design’s overall safety risk. The contractor shall address the identified hazards and recommend corrective actions. (CDRL A011)

7.0 OPERATIONS SECURITY (OPSEC):

7.1 Purpose:

OPSEC must be an integral part of our daily activities. As we maintain security on our future technologies that are vital to national interest, we must recognize and prepare for the threat poised against our technology. Department of Defense policies mandate a high degree of security throughout the acquisition process.

However, heightened security awareness and threat-based countermeasures are particularly essential during the research and development phase when our technology is most vulnerable to espionage, sabotage, or exploitation. It is the obligation of each employee or persons involved on this contract to be constantly aware of and strictly adhere to security requirements designed to protect sensitive unclassified and other information and resources produced by acquisition, research and development, and technological security efforts outlined in this SOO. The contractor shall ensure employees received training and follow appropriate OPSEC measures during the performance of this contract. (CDRL A010)

7.2 Coordination and Update:

The contractor shall develop an OPSEC plan to protect classified and unclassified sensitive data from exploitation. The contractor shall be responsible to coordinate on all OPSEC requirements and the OPSEC plan. The contractor shall also update the OPSEC plan when updated critical or other information is received including, as appropriate, at the sub-task level. The OPSEC plan shall apply to the contract. In addition, the contractor shall submit an updated SF 424 annually, or when new senior/key personnel are added. (CDRL A010, A019)

7.3 Compliance:

The contractor shall comply with the approved OPSEC plan. OPSEC surveys to measure the effectiveness of the OPSEC program may be conducted by the government. The contractor shall comply with these surveys. The contractor shall train personnel in, and follow appropriate OPSEC measures during, the performance of this contract. (CDRL A010)

8.0 PROGRAM & FINANCIAL MANAGEMENT:

The contractor shall exercise administration and management functions during this effort such as: scheduling of activities and milestones; describing status; outlining contractor activity and progress toward accomplishment of objectives; planning, forecasting, and making recommendations on funding and funding changes;

program planning; and describing in detail the conduct and overall results of this effort. The contractor shall ensure the documentation of this program by timely digital / photographic coverage of significant events and milestones. The contractor shall conduct annual reviews of this effort. (CDRLs A001, A002, A003, A004, A005, A006, A014, A016)

9.0 DIGITAL SYSTEMS ENGINEERING:

9.1 Integrated Digital Environment (IDE):

The contractor may establish and participate in an Integrated Digital Environment (IDE) in cooperation with other contractors and the government. The IDE may be responsible for enabling interface model/models incorporation, data exchange methodologies, and seamless digital thread integration across all involved parties.

The IDE may have contractor defined rules, project organization & management, model organization & customization, style, layout & naming conventions, and documentation requirements. (A018)

9.2 Model Based Systems Engineering (MBSE):

The contractor may use a SysML compatible solution capable of facilitating development of a MBSE model or models that defines the Authoritative Source of Truth (ASoT) for all necessary aspects of the conceptual system design. Access to view the MBSE system model and digital artifacts / models / threads being utilized on this program throughout the Period of Performance (PoP) may be available to the government via the appropriate shared system access. The MBSE system model may be presented in design reviews at the level of detail and fidelity required by the entrance and exit criteria for that review. The MBSE system model may have rule validation sets to drive toward automated systems engineering technical reviews, milestones, certifications, and integrity programs. (A008, A018)

9.3 Model Based Definition (MBD):

The contractor may use Computer Aided Design (CAD) software to document the Digital Product Definition (DPD) of all components and systems at the conceptual design level. The DPD may contain the fully annotated physical design of all components and systems to include dimensions, tolerances, materials, finishes and other notes to specify a complete product definition as defined in ASME Y14.41 Digital Product Definition Data Practices. The DPD may be ASoT data for physical designs of hardware in the MBSE System Model. The DPD may be appropriately connected via digital threads to ensure communication of DPD information between design disciplines. The DPD may be appropriately connected via digital threads to appropriate subcontractors to the greatest extent practical. (A008, A016, A018)

9.4 Digital Engineering Master Plan (DEMP):

The contractor shall develop a Digital Engineering Master Plan (DEMP), to include in the detailed research plan, that describes the contractor’s overall approach for setting up a collaborative digital environment and digital system engineering approach. This plan may include description of the digital threads, digital twins, tools, processes, and interfaces and their bi-directional traceability. The DEMP may define how the contractors will connect to government owned IT systems and/or extend contractor systems to government owned facilities at all appropriate security levels in a collaborative digital environment. (A016)

9.5 Conceptual Design Technical Data Package (TDP):

The contractor shall develop relevant data-centric deliverables generated in this effort that cover the models, data, and digital systems engineering products, representing the weapon system and associated engine concept. The TDP should include a level of detail appropriate to permit independent assessment the weapon system and associated engine concept designs in follow-on military utility studies.

Model, data, and products should be utilized and/or developed under the program to allow delivery of applicable source code to the maximum extent possible. (A008, A017)

9.6 Acquisition and Sustainment Data Package (ASDP):

The contractor shall capture a collection of relevant data-centric deliverables generated in this effort that cover the models, data, and digital systems engineering products created through the conceptual design process. The ASDP should include a level of detail appropriate to support follow-on independent research. Model, data, and products should be utilized and/or developed under the program to allow delivery of applicable source code to the maximum extent possible. (A018)

Additional Information regarding this SOO:

Based on funding projections, the Government plans to award up to 2 contracts. In the event additional funding becomes available, the Government may award additional contracts under this SOO.

Period of Performance:

30 months for the technical effort (plus 3 months for the Final Report)

Technical Performance Measures (TPM):

The technical performance measure, with proposed objective and threshold time criteria, for an engine vehicle conceptual design and assessment. This TPM supports the program objective to rapidly conduct rapid vision system studies, which offer new capabilities and reduces the turbine engine development timeline.

Technical Performance Parameter Threshold Objective

Engine Conceptual Design & Vehicle Integration Assessment Time

180 days 90 days

CDRL Requirements:

A001 Scientific and Technical Reports, Final Report (One-time) A002 Funds and Man-Hour Expenditure Reports (Monthly) A003 Contractor Spend and Expenditure Plan (Monthly) A004 Contract Funds Status Report (Quarterly) A005 Status Report (Quarterly) A006 Presentation Material (As requested) A007 Test Plan (As Requested) A008 Technical Data Package (As generated) A009 Scientific and Technical Reports, Interim Report (As generated) A010 Test / Inspection Report (As requested) A011 System Safety Hazard Analysis Report (As requested) A012 Detailed Research Plan (Once – 60 DACA, RASR) A013 Digital Imaging (As generated) A014 Operations Security (OPSEC) Plan (One-time) A015 Conceptual Design Drawings and Associated Lists (As generated) A016 Developmental Design Drawings and Associated Lists (As generated) A017 Gas Turbine Engine Steady State and Transient (As generated) A018 Acquisition and Sustainment Data Package (ASDP) (Annually) A019 Technical Information Report, SF 424 Annual Update (Annually)

Contract Type: Cost-Plus Fixed Fee, Firm-Fixed-Price, Cost Share, or Cost Reimbursement.

Earned Value Management System (EVMS): EVMS will not apply.

Security Classification: up to Secret as appropriate for each contract.

Government Research Facilities:

A list of available AFRL research facilities is included in the BAA. If the use of AFRL research facilities and their associated government and/or contractor operational work force are required to perform this contract, availability of these facilities including hardware requirements and/or facility modifications must be noted in the white paper and coordinated with the AFRL POC, prior to submission of 2nd Step full proposals.

Documentation of this coordination in the form of a letter must be included in the 2nd step full contract proposal. Research performed in an AFRL facility will not impact the above notional funding budget. If the use of Government R&D research facilities from a source other than AFRL/RQT is part of the offeror's plan, a coordination letter identifying availability of the research facilities and estimated costs from that government agency must be included in the contract proposal. Since this cost will be directly funded from AFRL to the other Government agency, the cost of performing the tasks will be subtracted from the notional budget identified above. Specific details regarding use of these research facilities are not considered final until completion of contract negotiations.

Government Furnished Property (GFP):

GFP is not anticipated. However, if GFP is required to perform contract tasks, it must be identified in white paper and availability for contract must be coordinated with the AFRL POC, prior to submission of 2nd Step proposals. Documentation of this coordination with must be included in the 2nd step contract proposal. If the use of GFP from a source other than AFRL/RQT is part of the offeror's plan, a coordination letter identifying availability of the GFP from that government agency must be included in the contract proposal. Specific details regarding use of GFP is not considered final until completion of contract negotiations.

White Paper Technical/Management Page Limitation: 5 pages

CLASSIFICATION (When filled in): Unclassified

PREVIOUS EDITION IS OBSOLETE. Page 1 of 4DD FORM 254, APR 2018

DEPARTMENT OF DEFENSE

CONTRACT SECURITY CLASSIFICATION SPECIFICATION

(The requirements of the National Industrial Security Program (NISP) apply to all security aspects of this effort involving classified information.)

OMB No. 0704-0567 OMB approval expires:

June 30, 2025

The public reporting burden for this collection of information, 0704-0567, is estimated to average 70 minutes per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Washington Headquarters Services, at whs.mc-alex.esd.mbx.dd-dod-information-collections@mail.mil. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number.

RETURN COMPLETED FORM AS DIRECTED IN THE INSTRUCTIONS.

1. CLEARANCE AND SAFEGUARDING

a. LEVEL OF FACILITY SECURITY CLEARANCE (FCL) REQUIRED (See Instructions)

Secret

b. LEVEL OF SAFEGUARDING FOR CLASSIFIED INFORMATION/

MATERIAL REQUIRED AT CONTRACTOR FACILITY

Secret

2. THIS SPECIFICATION IS FOR: (X and complete as applicable.)

a. PRIME CONTRACT NUMBER (See instructions.)

b. SUBCONTRACT NUMBER

c. SOLICITATION OR OTHER NUMBER

TBD

DUE DATE (YYYYMMDD)

3. THIS SPECIFICATION IS: (X and complete as applicable.)

a. ORIGINAL (Complete date in all cases.)

DATE (YYYYMMDD)

20230609

b. REVISED (Supersedes all previous specifications.)

REVISION NO. DATE (YYYYMMDD)

c. FINAL (Complete Item 5 in all cases.) DATE (YYYYMMDD)

4. IS THIS A FOLLOW-ON CONTRACT? No Yes If yes, complete the following:

Classified material received or generated under (Preceding Contract Number) is transferred to this follow-on contract.

5. IS THIS A FINAL DD FORM 254? No Yes If yes, complete the following:

In response to the contractor's request dated , retention of the classified material is authorized for the period of:

6. CONTRACTOR (Include Commercial and Government Entity (CAGE) Code)

a. NAME, ADDRESS, AND ZIP CODE

TBD

b. CAGE CODE

TBD

c. COGNIZANT SECURITY OFFICE(S) (CSO) (Name, Address, ZIP Code, Telephone required; Email Address optional)

7. SUBCONTRACTOR(S) (Click button if you choose to add or list the subcontractors -- but will still require a separate DD Form 254 issued by a prime contractor to each subcontractor)

a. NAME, ADDRESS, AND ZIP CODE

N/A

N/A

N/A

8. ACTUAL PERFORMANCE (Click button to add more locations.)

a. LOCATION(S) (For actual performance, see instructions.)

(If applicable, see Instructions.)

N/A

9. GENERAL UNCLASSIFIED DESCRIPTION OF THIS PROCUREMENT

The objective of this effort is to development an integrated engine vehicle conceptual design system that can be used to conduct integrated vision system studies to rapidly discover, assess, and design novel and unique propulsion architecture and technology that can both deliver new capability and significantly reduce the overall turbine engine development timeline. The integrated engine vehicle conceptual design system should leverage relevant digital engineering best practices as Model Based System Engineering (MBSE) and Multidisciplinary Analysis and Optimization (MDAO) to reduce the design and iteration time required for the development of a high confidence conceptual engine designs.

PREVIOUS EDITION IS OBSOLETE. Page 2 of 4DD FORM 254, APR 2018

10. CONTRACTOR WILL REQUIRE ACCESS TO: (X all that apply. Provide details in Blocks 13 or 14 as set forth in the instructions.)

a. COMMUNICATIONS SECURITY (COMSEC) INFORMATION f. SPECIAL ACCESS PROGRAM (SAP) INFORMATION

b. RESTRICTED DATA

g. NORTH ATLANTIC TREATY ORGANIZATION

(NATO) INFORMATION

c. CRITICAL NUCLEAR WEAPON DESIGN INFORMATION (CNWDI) (If CNWDI applies, RESTRICTED DATA must also be marked.)

h. FOREIGN GOVERMENT INFORMATION

d. FORMERLY RESTRICTED DATA

i. ALTERNATIVE COMPENSATORY CONTROL MEASURES

(ACCM) INFORMATION

e. NATIONAL INTELLIGENCE INFORMATION:

(1) Sensitive Compartmented Information (SCI)

(2) Non-SCI

j. CONTROLLED UNCLASSIFIED INFORMATION (CUI) (See instructions.)

k. OTHER (Specify) (See instructions.)

11. IN PERFORMING THIS CONTRACT, THE CONTRACTOR WILL: (X all that apply. See instructions. Provide details in Blocks 13 or 14 as set forth in the instructions.)

a. HAVE ACCESS TO CLASSIFIED INFORMATION ONLY AT

ANOTHER CONTRACTOR'S FACILITY OR A GOVERNMENT

ACTIVITY

(Applicable only if there is no access or storage required at contractor facility.

See instructions.)

b. RECEIVE AND STORE CLASSIFIED DOCUMENTS ONLY

c. RECEIVE, STORE, AND GENERATE CLASSIFIED

INFORMATION OR MATERIAL

d. FABRICATE, MODIFY, OR STORE CLASSIFIED HARDWARE

e. PERFORM SERVICES ONLY

f. HAVE ACCESS TO U.S. CLASSIFIED INFORMATION OUTSIDE

THE U.S.,PUERTO RICO, U.S. POSSESSIONS AND TRUST

TERRITORIES

g. BE AUTHORIZED TO USE THE SERVICES OF DEFENSE

TECHNICAL INFORMATION CENTER (DTIC) OR OTHER

SECONDARY DISTRIBUTION CENTER

h. REQUIRE A COMSEC ACCOUNT

i. HAVE A TEMPEST REQUIREMENT

j. HAVE OPERATIONS SECURITY (OPSEC) REQUIREMENTS

k. BE AUTHORIZED TO USE DEFENSE COURIER SERVICE

l. RECEIVE, STORE, OR GENERATE CONTROLLED UNCLASSIFIED

INFORMATION (CUI).

(DoD Components: refer to DoDI 5200.48, only for specific CUI protection requirements. Non-DoD Components: see instructions.)

m. OTHER (Specify) (See instructions.)

Pre-contract award access to classified is not required.

AFFARS 5352.204-9000 applies.

12. PUBLIC RELEASE

Any information (classified or unclassified) pertaining to this contract shall not be released for public dissemination except as provided by the National Industrial Security Program Operating Manual (NISPOM) or unless it has been approved for public release by appropriate U.S. Government authority.

Proposed public releases shall be submitted for review and approval prior to release to the appropriate government approval authority identified here with at least office and phone contact information and if available, an e-mail address. (See instructions)

DIRECT THROUGH (Specify below)

AFRL/RQ for non-SAR material. Transmission of public release request via e-mail is not authorized. Allow 23 days for processing.

Public Release Authority:

AFRL/RQ

2130 8th Street, WPAFB OH 45433

13. SECURITY GUIDANCE

The security classification guidance for classified information needed for this effort is identified below. If any difficulty is encountered in applying this guidance or if any other contributing factor indicates a need for changes in this guidance, the contractor is authorized and encouraged to provide recommended changes; to challenge the guidance or the classification assigned to any information or material furnished or generated under this contract;

and to submit any questions for interpretation of this guidance to the official identified below. Pending final decision, the information involved shall be handled and protected at the highest level of classification assigned or recommended.

(Fill in as appropriate for the classified effort. Attach, or forward under separate correspondence, any documents/guides/extracts referenced herein. The field will expand as text is added. When removing any expanded text area, use delete key or backspace key, then click out of the text field for it to shrink after the text has been deleted. Also allows for up to 6 internal reviewers to digitally sign. See instructions for additional guidance or use of the fillable PDF.)

32 Code of Federal Regulations, Part 117, National Industrial Security Program Operating Manual (NISPOM), 24 February 2021, applies.

SECURITY GUIDANCE:

Ref Item 10a: Contractor will comply with AFMAN 17-1302-O, Communications Security (COMSEC) Operations, 9 Apr 20. Contractor personnel will follow the security requirements of the host government activity. Access to classified COMSEC information requires a final U.S. Government clearance at the appropriate level. Further disclosure of COMSEC information by a contractor, to include subcontracting, requires prior approval of the GCA. Non-accountable COMSEC information, though not tracked in the COMSEC material control system, may still require a level of control within a document control system. Refer to NSA/CSS Manual 3-16, “Control of Communications Security Material,” and the Committee on National Security Systems Instruction (CNSSI) 4001, “Controlled Cryptographic Items,” for guidance.

Ref Blk 10e(2): Contractor will require access to intelligence information and must comply with directions provided by the Program

PREVIOUS EDITION IS OBSOLETE. Page 3 of 4DD FORM 254, APR 2018

Manager (PM). The Program Manager has determined that disclosure does not create an unfair competitive advantage for the contractor or a conflict of interest with the contractor's obligation to protect the information. The PM will identify what intelligence information is required for the contractor to satisfy the contract and will submit that information to the AFRL/RQ servicing Senior Intelligence Officer at AFRL/RQ for approval prior to granting access.

Ref Blks 10j/11l: The contractor shall comply with DoDI 5200.48, Controlled Unclassified Information; AFMAN 16-1404, volume 1, Operations Support, Information Security Program: Overview, Classification, and Declassification; Air Force Guidance Memorandum 2020-16-01, Air Force Guidance Memorandum for CUI, 23 July 2020; and DoDM 5400.7-Air Force Manual 33 302, DoD Freedom of Information Act (FOIA) Program. The contractor shall monitor CUI aggregation and compilation based on the potential to generate classified information pursuant to security classification guidance addressing the accumulation of unclassified data or information.

Ref Item 11c: Contractor will reference the appropriate security classification guidance when generating or deriving classified material or hardware. All classified information received or generated will be properly stored and handled according to the markings on the material.

All classified information received or generated is the property of the U.S. Government. At the termination or expiration of the contract, the U.S. Government will be contacted to proper disposition instructions. Contractor will abide by the following security classification guidance: 1) Air Breathing Turbine Engine Aircraft and Missile Propulsion SCG, OPR AFRL/RQT, Revised 5 Nov 2020; 2) High Speed Technology Development SCG, OPR AFRL/RQH, 8 Mar 2021; and 3) Guided Weapons Technology SCG, OPR, AFRL/RW, 1 Nov 2011 All SCGs will be provided under separate cover.

Ref Blk 11d: The contractor is required to provide adequate and approved storage for classified hardware or material to the level of SECRET which because of size or quantity cannot be safeguarded in an approved storage container. This is only required if awarded a contract. This is not required or necessary during the solicitation period.

Ref Blk 11m: Provide the information requested by the Notification of Government Security Activity and Visitor Group Security Agreements clause, Air Force Federal Acquisition Regulation Supplement (AFFARS) 5352.204-9000, to AFRL/RQOS the Servicing Security Activity (SSA), 2130 8th Street, WPAFB OH 45433 AFRL.RQEastDL-Security@us.af.mil. The contractor shall comply with DoDM 5220.22 Vol 2_AFMAN 16-1406 Vol 2, National Industrial Security Program: Industrial Security Procedures for Government Activities, 8 May 20, by following security procedures of the installation IAW para 3.8.a.; report adverse information IAW para 4.14 (Added)(AF); and support commander self-inspections and self-assessments IAW para 14.1.f (Added)(AF). See attached security agreement.

* AFRL/RQ Security (RQOS) office must approve further disclosure of information covered under this effort, to include subcontracting.

* Upon the end of this effort, the contractor shall contact the AFRL/RQOS for disposition instructions of classified access or material generated or received during this effort.

* Any classified or covered defense information under this effort cannot be transferred or used for another effort to include IRAD, unless express written approval is received from AFRL/RQ PM or AFRL/RQOS.

*Contractor personnel shall utilize US Government or official company email for transmitting official US Government business/ information. US Government information shall NOT be transmitted via personal, private or commercial email or social media accounts (e.g. Hotmail, Gmail, Yahoo, Tik Tok, Facebook etc.). The use of DOD Safe is authorized for unclassified and Controlled Unclassified Information only.

*Contractor personnel are strictly prohibited from referencing this contract, classification, clearances, accesses (SAP/SAR, SCI), in advertisements, websites, capability fliers, promotional efforts or even in retirement notifications of employees.

Program Manager: Eric Faith, AFRL/RQTE, (937) 255-7510, eric.faith@us.af.mil Administrative Contracting Officer: Peter Seiley, AFRL/RQKPB, (937) 713-9943, peter.seiley@us.af.mil Security Manager: Lucinda Coleman, AFRL/RQOS, (937) 904-8609, lucinda.coleman@us.af.mil; David Hanson, AFRL/RQOS, (937) 938-4921, david.hanson.17@us.af.mil

List of Attachments (All Files Must be attached Prior to Signing, i.e., for any digital signature on the form)

RQOS- Security Coordination

NAME & TITLE OF REVIEWING OFFICIAL

Dennis Reed Chief of Security, AFRL/RQOS

SIGNATURE

14. ADDITIONAL SECURITY REQUIREMENTS

PREVIOUS EDITION IS OBSOLETE. Page 4 of 4DD FORM 254, APR 2018

Requirements, in addition to NISPOM requirements for classified information, are established for this contract.

No Yes If Yes, identify the pertinent contractual clauses in the contract document itself, or provide an appropriate statement which identifies the additional requirements. Provide a copy of the requirements to the CSO. The field will expand as text is added or you can also use item 13. When removing any expanded text area, use delete key or backspace key, then click out of the text field for it to shrink after the text has been deleted.

(See instructions for additional guidance or use of the fillable PDF.)

Ref Blk 11j: OPSEC requirements apply.