Call for MASTR 27 Jan 25.pdf

FA2391-23-S-2403

MASTR CALL

FA2391-23-S-2403

Pioneering Aerospace Capabilities, Engineering and Research (PACER)

CALL:

Multidisciplinary, Aerodynamics, and Structures Technologies Research (MASTR)

27 JAN 2025

OVERVIEW INFORMATION

Broad Agency Announcement Type:

The PACER BAA FA2391-23-S-2403. Offerors should monitor www.SAM.gov for any additional notices or modifications to this CALL announcement.

NAICS Code:

The NAICS Code for this acquisition is 541715 (Research and Technology in the Physical, Engineering, and Life Sciences (except Nanotechnology and Biotechnology), and the small business size standard is 1,000 employees. The following Small Business Administration (SBA) size standard exceptions may apply: Aircraft, Aircraft Engine and Engine Parts is 1,500 employees; Other Aircraft Parts and Auxiliary Equipment is 1,250 employees; and Guided Missiles and Space Vehicles, Their Propulsion Units and Propulsion Parts is 1,300 employees.

Federal Agency Name:

Air Force Research Laboratory, Aerospace Systems Directorate, AFRL/RQ

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 during the PACER BAA Open Period covering the topic specified in this CALL, “RQV Topic 18 – Multidisciplinary Design, Analysis and Optimization (MDAO)” will be accepted.

DUE DATE AND TIME:

CALL (solicitation): PROPOSAL DUE DATE AND TIME: Tuesday, 01 APRIL 2025, 1:00 P.M. local time, Wright-Patterson AFB, OH.

Submission:

Proposals must be submitted to the Primary Contracting Point of Contacts (POCs):

Contracting Officer, AFRL/RQKPC Erin Plessinger; erin.plessinger@us.af.mil Contract Specialist, AFRL/RQKPC, Sal Spinier; sal.spanier@us.af.mil

Electronic submission is required. Offerors, please request a DoD Safe Drop-Off link by email to sal.spanier@us.af.mil at least 4 calendar days prior to Proposal 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 or Other Transaction (OT) for Prototype, grant, cooperative agreement, or OT for Research. The Air Force may also consider award of an appropriate technology transfer mechanism if applicable. It is anticipated that awards under this CALL will likely be Multiple Award Fair Opportunity (MAFO) IDIQ contracts with Cost Plus Fixed Fee (CPFF), Cost Reimbursement, Cost Share (at the discretion of the offeror), and/or Firm Fixed Price (FFP) task orders. Cost reimbursement contracts require successful offerors to have an accounting system considered adequate for tracking costs applicable to the contract. The IDIQ minimum guarantee required by FAR 16.504(a)(1) will be the initial Task Order solicited with this CALL. We anticipate that the initial task order will be a CPFF type task order.

Estimated Total Program Cost:

Shared IDIQ ceiling of $200M (for the program; not per contract).

http://www.sam.gov/ mailto:erin.plessinger@us.af.mil mailto:sal.spanier@us.af.mil

Anticipated Number of Awards:

The Air Force anticipates one or more Multiple Award IDIQ awards for this CALL. 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 Multidisciplinary, Aerodynamics, and Structures Technology Research (MASTR)

IDIQ:

The objective of MASTR IDIQ is to conduct basic, applied, advanced, and demonstration / validation research to develop and demonstrate, integrate, and transition new aerospace vehicle technologies to the warfighter. These technologies include advanced research and development in structures, aerodynamics, and multidisciplinary science and technologies. The goal of these technology advancements is to improve cost effectiveness, increase vehicle survivability, increase mission performance, and introduce new capabilities. Task Orders shall be used to conduct basic, applied, advanced, and demonstration/validation research and technology development in the following AFRL/RQV technical competencies/research areas.

Technical Competencies/Research Areas List:

• Multidisciplinary Science & Technology

• Classified Design and Experimental Studies

• Structures Technology

• Aerodynamic Technologies o Weapons Integration o Airframe Propulsion Integration o Advanced Aerodynamic Technologies o Advanced Aerodynamic Design and Analysis o Aerodynamic Experimentation & Validation

• Systems Engineering

Brief Program Summary MASTR - Capabilities Study Initial Task Order:

Through the use of the Capabilities Study Task Order, under the Multidisciplinary, Aerodynamics, and Structures Technologies Research (MASTR) IDIQ, AFRL/RQV will conduct basic, applied, advanced, and demonstration/validation research and technology development in the following technical competencies/research areas (see MASTR Basic IDIQ SOO for further details on each of these technical areas): Multidisciplinary Science & Technology, Classified Design and Experimental Studies, Structures Technology, Aerodynamic Technologies, Systems Engineering. Research and technology development in these technical competencies may require the use of technology demonstration vehicles, ground test facilities, flight test facilities, and/or laboratory experiments to develop, analyze, and assess aerospace vehicle structures technologies for transition to the warfighter.

Technical Requirements/Tasks:

• Identify Technology Gap and Conceptual Research Project

• Define Strategy for Increased Security Levels

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

Contracting POCs Erin Plessinger Contracting Officer

AFRL/RQKPC

erin.plessinger@us.af.mil

Sal Spanier Contract Specialist

AFRL/RQKPC

sal.spanier@us.af.mil mailto:erin.plessinger@us.af.mil

FULL TEXT ANNOUNCEMENT:

1. PROGRAM DESCRIPTION:

Air Force Research Laboratory, AFRL/RQV, The Aerospace Vehicles Division, is soliciting IDIQ and Task Order Proposals on the following research effort: RQV Topic #18 Multidisciplinary, Aerodynamics, and Structures Technologies Research (MASTR)

1.1. Statement of Objectives: See the following Attachments:

Attachment 1 MASTR IDIQ Statement of Objectives (SOO) Attachment 2 MASTR Capabilities Study Initial Task Order SOO

This effort falls within the PACER BAA (FA2391-23-S-2403), Technical Objective Area RQV Topic 18 – Multidisciplinary Design, Analysis and Optimization (MDAO).

RQV Topic 18 – Multidisciplinary Design, Analysis and Optimization (MDAO):

Discover, develop and demonstrate MDAO methods and technologies to enable next-generation aerospace vehicles and provide Air Force decision makers risk-quantified effectiveness assessments of concepts and technologies. Areas of interest include but are not limited to multidisciplinary, multi-fidelity system level effectiveness based design optimization, risk-quantified multi-fidelity coupled analyses and sensitivities, goal oriented adaptive analyses, risk-quantified gradient and non-gradient based design space exploration including machine learning, physics- and statistics-based Reduced Order Models (ROMs), optimization methods, uncertainty quantification methods, model based systems engineering, robust model construction methods, data assimilation methods, digital engineering design methods, multidisciplinary technologies (such as active aeroelastic wing, active flutter suppression, multifunctional structures, etc..), additive manufacturing for design and testing, and experimental validation via ground or flight testing.

1.2. Within Scope Modification:

Potential offerors are advised that due to the inherent uncertainty of research and development efforts, awards resulting from this announcement may be modified during performance to make within scope changes, to include but not limited to, modifications which increase overall contract ceiling amount and modifications under authority of DFARS 235.006-71.

1.3. Deliverable Items:

1.3.1. Data Items:

Contract Data Requirements List (CDRL):

CDRL Title A001 Scientific and Technical Reports - Final Report

A002 Contract Funds Status Report (CFSR)

A003 Funds and Man-Hour Expenditure Report

A004 Contractor Spend and Expenditure Plan

A005 Project Planning Chart

A006 Status Report

A007 Scientific and Technical Reports - Interim Report

A008 Presentation Material

A009 Test Plan

A010 Test Procedure

A011 Scientific and Technical Reports - Flight Test Data

A012 Software Design Description (SDD)

A013 Software Development Plan (SDP)

A014 Software User Manual (SUM)

A015 Data Base Design Description (DBDD)

A016 Data Accession List (DAL)

A017 System/Subsystem Design Description (SSDD)

A018 Developmental Design Drawings/Models and Associated Lists

A019 Computer Software Product

A020 Material and Processing Digital Data Package (MPDDP)

A021 Technical Report-Study/Services

A022 Interface Design Description (IDD)

A023 Interface Requirements Specification (IRS)

A024 Computational Aerodynamic Model (CAM)

A025 System Architecture Model (SAM)

A026 Interface Control Document (ICD)

A027 Flight Flutter Test Report

A028 Internal Loads and Static Strength Analysis Report

A029 Software Test Description (STD)

A030 Software Test Plan (STP)

A031 Software Test Report (STR)

A032 Management Plan

A033 Report, Record of Meeting/Minutes

A034 Cost Data Summary Report (CDSR) (DD Form 1921)

A035 Computer Operation Manual (COM)

A036 Computer Software Product End Items - Data Base

A037 Firmware Support Manual (FSM)

A038 Software Center Operator Manual (SCOM)

A039 Software Input/Output Manual (SIOM)

A040 Software Product Specification (SPS)

A041 Software Quality Assurance Report

A042 Software Requirements Specification (SRS)

A043 Software Version Description (SVD)

A044 System Safety Hazard Analysis Report (SSHA)

A045 System Engineering Management Plan (SEMP)

A046 Test Plans/Test Procedures

A047 Operations Security (OPSEC) Plan

A048 Program Protection Implementation Plan (PPIP)

A049 Scientific and Technical Reports: Critical Technologies Identification Assessment

A050 Software Resources Data Reporting (SRDR): Development, Maintenance and Enterprise Resource Planning Development Reports, and Data Dictionary

A051 Software Resources Data Reporting: Final Developer Report and Data Dictionary

A052 Software Resources Data Reporting: Initial Developer Report and Data Dictionary

A053 Engineering Data for Provisioning (EDFP)

A054 Flutter Analysis Report

A055 Briefing Material

A056 Computational Aerodynamics Analysis Results A057 Airworthiness Compliance Report A058 Airworthiness Certification Basis

A059 Commercial Derivative Aircraft (CDA) Airworthiness Certification Data

A060 System/Software Integration Laboratory (SSIL) Development Management Plan

A061 Airframe Rigidity Test Report

A062 Durability and Damage Tolerance (DADT) Analysis Report

A063 Durability and Damage Tolerance (DADT) Test Report

A064 Software Development Summary Report

A065 Cybersecurity Implementation Plan

A066 Security Classification Guide

A067 Federal Aviation Administration Airworthiness Substantiation Data

A068 Commercial Engineering Design Data and Associated Lists

A069 Scientific and Technical Reports: Security Plan

A070 Scientific and Technical Reports: R&R Annual Update

*See Attachment 5 for the Contract Data Requirements List

1.3.2. Hardware:

Test articles, subcomponents, tooling, geometry data, etc. Hardware will be managed with a contract line-item number.

1.3.3. Software:

Design tools, analysis tools, simulation, and experimentation development, etc. Software will be managed with a contract line-item number.

1.4. Period of Performance:

Basic IDIQ PoP:

• Overall PoP: 132 months

• Ordering Period: 120 months

Initial TO PoP:

• Overall PoP: 6 months

• Technical Period of Performance: 3 months

• Reporting: 3 months

1.5. Other Requirements:

1.5.1. Program Security Classification:

Secret DD Form 254 Contract Security Program Specifications Attachment 4. Offerors must verify their Cognizant Security Office information is current with Defense Counterintelligence and Security Agency (DCSA) at www.dcsa.mil.

1.5.2. OPSEC:

Operations Security (OPSEC) requirements, per the PACER BAA, FA2391-23-S-2403, (Revision 1) dated 5 June 2024 (page 10), shall be incorporated into the Statements of Work.

1.5.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, Military Critical Technical Data Agreement, is required to be submitted with the Proposal.

1.5.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. The contractor must have an active DD Form 2345, Militarily Critical Technical Data Agreement, and a NIST 800-171 assessment in SPRS.

1.5.5. Contractor Performance Assessment Reporting System (CPARS):

Not Applicable.

1.6. The below provisions/clauses shall be included, but not limited to the following:

• FAR 52.204-27 Prohibition on a ByteDance Covered Application (Full Text)

• DFARS 252.204-7008 Compliance with Safeguarding Covered Defense Information Controls (Full

Text)

• DFARS 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting

(Full Text)

• DFARS 252.204-7018 Prohibition of the Acquisition of Covered Defense Telecommunications

Equipment or Services (Full Text)

• DFARS 252.204-7019 NIST SP 800-171 DoD Assessment Requirements – Please be aware the offeror is required to implement NIST SP 800-171 pursuant to DFARS Clause 252.204-7012 (Full Text)

• DFARS 252.204-7020 NIST SP 800-171 DoD Assessment Requirements

• DFARS 252.215-7009 Proposal Adequacy Checklist

• DFARS 252.228-7001 Ground and Flight Risk (Full Text)

• H0023 Air Force Research Laboratory – Wright Research Site Security Requirements (JUN 2023)

(Full Text)

1.7. Other Information:

1.7.1. Government Furnished Property (GFP):

GFP is not anticipated to be made available for the Initial Task Order. However, if future Task Orders would benefit from the use of GFP, in accordance with FAR 45.201(b), the contractor is responsible for all costs related to making the property available for use, such as payment of all transportation, installation or rehabilitation costs.

1.7.2. Government Furnished Information (GFI):

Not Anticipated on Initial Task Order. If required must be identified in the Proposal.

1.7.3. Base Support/Network Access:

TBD for future Task Orders.

1.7.4. Data Rights Desired:

http://www.dcsa.mil/

Noncommercial Technical Data: To Be Determined Noncommercial Computer Software (NCS): To Be Determined NCS Documentation: To Be Determined Commercial Computer Software Rights: To Be Determined

The Air Force Research Laboratory is engaged in the discovery, development, and integration of warfighting technologies for our air, space, and cyberspace forces. As such, rights in noncommercial technical data and NCS developed or delivered under this contract are of significant concern to the Government. The Government will therefore evaluate any restrictions on the use of noncommercial technical data, NCS, and NCS documentation which could result in transition difficulty or less-than full and open competition for subsequent development of this technology.

In accordance with DFARS 252.227-7013(b)(1) and 252.227- 7014(b)(1), the Government shall receive unlimited rights in all noncommercial technical data and computer software developed exclusively with Government funds.

In accordance with DFARS 252.227-7013(b)(2) and DFARS 252.227- 7014(b)(2), the Government shall receive Government Purpose Rights (GPR) in all noncommercial technical data and computer software developed with mixed funding. “Developed with mixed funding” means, “development was accomplished partially with costs charged to indirect cost pools and/or costs not allocated to a government contract, and partially with costs charged directly to a government contract.” Offerors that propose delivery of noncommercial technical data, NCS, or NCS documentation subject to GPR should fully explain how a portion of the data was developed at private expense. Specifically, offerors must explain what noncommercial technical data, NCS, or NCS documentation developed with costs charged to indirect cost pools and/or costs not allocated to a Government contract will be incorporated, how the incorporation will benefit the program, and address whether those portions or processes are segregable.

Offerors that propose delivery of noncommercial technical data with Limited Rights, NCS with Restricted Rights, or NCS documentation with Limited Rights will be considered. Proposals should fully explain what noncommercial technical data, NCS, or NCS documentation developed with costs charged to indirect cost pools and/or costs not allocated to a Government contract will be incorporated and how the incorporation will benefit the program and whether those portions or processes are segregable.

Offerors shall include the data rights assertions as required by DFARS 252.227-7017, Identification and Assertion of Restrictions on the Government’s Use, Release, or Disclosure of Technical Data or Computer Software. The assertions list is included in Section K and due at time of proposals. Assertions must be completed with specificity. Each assertion must identify the technical data or computer software to be delivered, and the associated item, component, or process developed exclusively or partially at private expense to which it pertains. Nonconforming data rights assertion lists will not be accepted until submitted in accordance with DFARS 252.227-7017.

Terms used in this section are defined in the clauses at 252.227-7013, Rights in Technical Data- Noncommercial Items, and 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation.

THIRD PARTY SOFTWARE (COMMERCIAL AND NONCOMMERCIAL):

If any such software, noncommercial or commercial, is not reasonably identifiable at proposal submission, it must still be approved by the contracting officer prior to incorporation. This obligation to obtain pre- approval by the contracting officer, as described above, continues throughout contract administration.

Noncommercial Computer Software:

DFARS 252.227-7014(d) describes requirements for incorporation of third party noncommercial copyrighted computer software and computer software documentation and is incorporated as follows: The Contractor shall not, without the written approval of the Contracting Officer, incorporate any copyrighted computer software or computer software documentation in the software or documentation to be delivered under this contract unless the Contractor is the copyright owner or has obtained for the Government the license rights necessary to perfect a license or licenses in the deliverable software or documentation of the appropriate scope set forth in DFARS 252.227- 7014(b), and prior to delivery of such -

a. Computer software, has provided a statement of the license rights obtained in a form acceptable to the Contracting Officer;

or

b. Computer software documentation has affixed to the transmittal document a statement of the license rights obtained.

In addition, all noncommercial computer software will receive the appropriate level rights set forth in DFARS 252-7014(b), which could include: Unlimited rights, GPR, Restricted Rights, or specifically negotiated license.

Commercial Computer Software:

For commercial computer software, the Government will neither accept nor execute a DD Form 250 for such software deliverables until the Contractor obtains from all third party software suppliers and/or vendors (Licensor) licenses for any commercial computer software to be delivered that are consistent with Federal Statutes, Federal Case Law, and Federal Regulations.

The following is a non-exhaustive list of terms and conditions which are inconsistent with Federal law and shall not be included in the commercial computer software license agreement between the Licensor and the Government:

1 The license shall not subject the Government to a contingent liability or a liability that is indefinite or indeterminate, including but not limited to: indemnification clauses, unilateral price increases, the right to attorney fees, automatic assessment of charges, or automatic renewal provisions. These provisions constitute obligations in advance or in excess of an appropriation and violate the Anti-Deficiency Act.

2 The license shall be governed by Federal Statutes, Federal Case Law, and Federal Regulations, and shall not be subject to the laws or jurisdiction of any municipality, state, or foreign country. The license shall not bind the Government to litigation in a particular forum or venue or require the Government to participate in arbitration.

3 The license shall not include non-substitution language that would preclude or limit the Government from using another vendor/reseller and/or product to fulfill Government requirements.

4 The Licensor shall not have the authority to unilaterally terminate the license. All remedies available shall be consistent with the Disputes and Termination Clauses in the underlying basic contract.

5 The Licensor shall not have the right to enter the premise or monitor Government networks for the purpose of auditing the use of the license.

6 The Licensor shall not have the authority to control or otherwise influence any litigation between a third party and the Government. The United States Department of Justice has the sole authority to represent the Government in all litigation matters.

7 The Licensor shall not use the fact that the Government is using the Licensor's products in any notification or advertisement to the public (e.g., no publicity rights permitted).

8 The license shall not require automatic updates or give Licensor the authority to unilaterally replace the software.

[IF APPLICABLE] Additionally, the Contractor may be required to obtain licenses that comply with the following terms and conditions, based on the Government’s needs 1 [IF APPLICABLE] The license shall not disclaim all warranties through use of an “as is” provision.

2 [IF APPLICABLE] The license shall neither restrict the Government from using the product at various sites nor limit use of the product by various Government agencies or third parties performing work on behalf of the Air Force under the [PROGRAM NAME]. In performance of the [PROGRAM NAME], Government personnel as well as Government contractors may use the software, subject to any negotiated limits on number of users, as applicable.

3 [IF APPLICABLE] [The license shall not limit the Government’s use of the software at other Government and Government contractor sites.] [The license shall authorize the Government to use the software at the following sites: [list].

4 [IF APPLICABLE] The license shall not restrict the Government from copying or embedding elements of accessible code into other applications (e.g., nesting code, derivative works).

The Contractor may obtain agreement from the Licensor to insert the clause below in its respective software licenses intended to be transferred to the Government:

“In the event that any of the provisions of the [Software License] are determined to be inconsistent with Federal law or do not otherwise satisfy the Government's needs, the parties to the [Software License] hereby agree that such provisions shall be null and void as they pertain to the Government. Specifically, the following sections are hereby deleted from the [Software License] [and/or amended as indicated below]:

[Section X: deleted; Section Y: amended as follows […]” If the Licensor will not agree to the terms and conditions cited herein and/or as contained in DFARS 227.72, the Contractor shall retain the current license on behalf of and for the benefit of the US Government if permissible under its license and such use will not subject the Government to the terms of the license. If the software in question is required to be delivered to the Government, the Licensor must grant the Government a sublicense that allows the Government to use the software to meet its requirements.

The Contractor shall provide documentation to clearly correlate or map any commercial computer software to be delivered to:

1.1. Contract Line-Item Numbers (CLINS);

1.2. Contract Deliverables (CDRLS);

1.3. Paragraphs in the statement of work (SOW); and

1.4. Portions of any functional block diagrams and/or system architecture diagrams, so that it can be readily determined where certain commercial computer software corresponding to certain software license agreement(s) are physically located on the system to be delivered under the contract.

2. AWARD INFORMATION:

2.1. Anticipated Award Date: Anticipated contract award date is approximately AUGUST 2025.

2.2. Anticipated Funding: CAPABILITIES STUDY TASK ORDER range of $10,000-$15,000.

3. ELIGIBILITY INFORMATION:

See PACER BAA FA2391-23-S-2403

4. PROPOSAL SUBMISSION INFORMATION:

Overview: This CALL is One-Step CALL. Proposals will be solicited via THIS CALL.

4.1. CALL - Proposal Instructions:

4.1.1. General Instructions: This CALL consists of offerors submitting Technical and Cost/Business Proposals for the following:

• MASTR IDIQ (plus the following Initial Task Order)

• MASTR Capabilities Study Initial Task Order

*To be eligible for award the USAF must receive a technical and cost proposal for the IDIQ and a technical and cost proposal for the Initial Task Order.

After receipt, Proposals will be evaluated in accordance with the award criteria in Section 4.1.2. below.

Proposals will be categorized and subsequently elected for negotiations.

4.1.2. Technical/Management and Cost/Business volumes should be submitted in separate volumes and MUST be valid for at least 225 days. Offerors MUST state this on the cover page of each volume of their proposal. IDIQ TO AND SPECIFIC BY TASKS. OFFERORS MUST SUBMIT A TO PROPOSAL

ALONG WITH THE IDIQ PROPOSAL.

4.1.2.1.

Specific Proposal Submission Instructions:

To be eligible for award the USAF must receive a technical and cost proposal for the Basic IDIQ (MASTR) AND a technical and cost proposal for the Capabilities Study Initial Task Order.

Combined proposals will not be accepted. Technical/Management and Cost/Business volumes should be submitted in separate volumes and MUST be valid for at least 225 days. Offerors MUST state this on the cover page of each volume of their proposal.

After receipt, Proposals will be evaluated in accordance with the award criteria below. Proposals will be categorized and subsequently elected for negotiations.

Offerors should apply the restrictive notice prescribed in FAR 52.215-1(e) Instructions to Offerors—Competitive Acquisition. Offerors should consider proposal instructions contained in the Broad Agency Announcement (BAA) Guide for Industry, which can be accessed on line at https://www.afrl.af.mil/Portals/90/Documents/HQ/BAA%20Ind%20Guide%202020.pdf?ver=7AivkWvoUoptKgypgCuIv w%3d%3d This guide is specifically designed to assist the offeror in understanding the BAA proposal process.

• REMINDER: To be eligible for award the USAF must receive a technical and cost proposal for the Basic

IDIQ (MASTR) and a technical and cost proposal for Capabilities Study Initial Task Order.

4.1.3. Proposals MUST reference the announcement number FA2391-23-S-2403, CALL Name, and the relevant Topic Number.

4.1.4. Offerors MUST submit one electronic copy of their Proposals per the directions in the Request for Proposal. Please contact the Contracting POC identified in the CALL if there are any issues submitting an electronic copy.

4.1.5. The cost file(s) spreadsheets must be in Microsoft Excel and include the formulas for calculating cost element bases (i.e., G&A, O/H, etc.)

4.1.6. Offerors are advised that only Contracting Officers are legally authorized to contractually bind or otherwise commit the Government.

4.1.7. The cost of preparing Proposals in response to this BAA is not considered an allowable direct charge to any resulting or any other contract; however, it may be an allowable expense to the normal bid and proposal indirect cost as specified in FAR 31.205-18.

4.1.8. No classified technical proposals or cost volumes are expected. Offerors are encouraged to keep all elements of the proposal package unclassified. In the rare case where an offeror has a need to submit a classified appendix, please contact the Technical POC identified in the CALL for delivery instructions.

4.2. Technical/Management Proposal:

4.2.1. IDIQ AND TASK ORDER (TO) INSTRUCTIONS:

4.2.1.1. Page Limitations: The following describes proposal page limitations.

a. The Technical/Management Proposal shall be limited to 25 pages. Technical/Management proposals and Statements of Work must be provided in Microsoft Word. Signed pages may be submitted in Adobe.

b. Font shall be standard 10-point business font Arial.

c. Character spacing must be “normal,” not condensed in any manner.

d. Pages shall be double-spaced (must use standard double-space function in Microsoft Word), double sided (each side counts as one page), 8.5 by 11 inches, with at least one-inch margins on both sides, top and bottom.

e. 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.

f. Pages shall be numbered starting with the cover page being Page 1, and the last page being no greater than 25. 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.

https://www.afrl.af.mil/Portals/90/Documents/HQ/BAA%20Ind%20Guide%202020.pdf?ver=7AivkWvoUoptKgypgCuIvw%3d%3d https://www.afrl.af.mil/Portals/90/Documents/HQ/BAA%20Ind%20Guide%202020.pdf?ver=7AivkWvoUoptKgypgCuIvw%3d%3d

g. The proposal page limit does not include the offeror’s proposed Statement of Work (SOW);

however, the same formatting rules apply to the SOW, which is limited to 10 pages.

h. Please Note: The Government will check the Proposal and SOW for conformance to the stated requirements. Any pages in excess of the stated page limitation after the format check will not be considered for review purposes.

4.3. Technical/Management Proposal:

4.3.1. The Technical/Management proposal(s) shall include a discussion of the nature and scope of the research and the technical approach. Additional information on prior work in this area, descriptions of available equipment, use of base support (if requested), data and facilities and resumes of personnel who will be participating in this effort should also be included as attachments to the technical proposal.

These volumes shall include a SOW detailing the technical tasks proposed to be accomplished under the proposed effort and suitable for contract incorporation. Do not include any proprietary information in the SOW. Refer to the BAA Guide for Industry referenced above to assist in SOW preparation. In addition to the contractor proposed SOW, a Government generated Supplemental SOW containing additional contracting requirements will be included in any resulting contracts (See PACER BAA Attachment 8).

4.3.2. Any questions concerning the technical proposal or SOW preparation shall be referred to the

Technical POCs listed in the CALL.

4.4. Cost/Business Proposal:

4.4.1. Separate the Proposal into a business section and cost section. If adequate price competition does not exist, and the threshold for a negotiated contract is equal to or expected to exceed $2,000,000.00, submission of certified cost or pricing data may be required.

a. See PACER BAA Attachment 2 for the Model Contract. Note: The document awarded may include contract line items (CLINs)/clauses/articles in addition to those in the model, and/or some of the CLIN/clauses/articles in the model may be deleted, depending on the specific circumstances of the individual award. Any additions or deletions will be negotiated with the offeror prior to award.

b. Business section: should contain all business aspects to the proposed contract, such as type of contract, any exceptions to terms and conditions of the announcement including the model contract, any information not technically related, etc. Provide rationale for exceptions.

c. Associate Contractor Agreements: Associate Contractor Agreements (ACAs) are agreements between contractors working on Government contracts that require them to share information, data, technical knowledge, expertise, or resources. The contracting officer may require ACAs when contractors working on separate Government contracts must cooperate, share resources or otherwise jointly participate in working on contracts or projects. Prime contractor to subcontractor relationships do not constitute ACAs. For each award, the contracting officer will identify associate contractors with whom agreements are required.

d. Identify any technical data that will be delivered with less than unlimited rights.

e. Subcontracting Plans: For efforts to exceed $750,000, Subcontracting Plans shall be submitted in the cost/business proposal. Reference FAR 19.704 and DFARS 219.704 for subcontracting plan requirements. Small business concerns are exempt from this requirement. If an IDIQ contract arrangement is anticipated, the basis for the subcontracting plan should reflect the entire ceiling amount.

f. Limitations on Pass-Through Charges: As prescribed in FAR 15.408(n)(1) & 15.408(n)(2), provisions 52.215-22, “Limitations on Pass Through Charges- Identification of Subcontract Effort (Oct 2009),” apply.

g. Completed Certifications and Representations: (Section K) are due with the Proposal.

Certifications and Representations (Section K) Attachment 6. Offerors may also be required to submit updated or supplemental Certifications and Representations based on the specifics of their proposal.

4.4.2. If an offeror proposes the use of GFP, the offer must specifically identify each piece of GFP in the

Cost/Business Proposal and propose and substantiate a rental cost for evaluation purposes in accordance with FAR 45.202. Include the following information in the proposal:

a. A list describing all Government property that the offeror or its subcontractors propose to use on a rent-free basis. The list shall identify the accountable contract under which the property is held and the authorization for its use (from the contracting officer having cognizance of the property);

b. The dates during which the property will be used and, for any property that will be used concurrently in performing two or more contracts, the amounts of the respective uses in sufficient detail to support prorating the rent

c. The amount of rent that would otherwise be charged in accordance with FAR 52.245-9, Use and Charges; and

d. The voluntary consensus standard or industry leading practices and standards to be used in the management of Government property, or existing property management plans, methods, practices, or procedures for accounting for property.

4.4.3. Cost Element Breakdown: Clear, concise, and accurate cost proposals reflect the offeror's financial plan for accomplishing the effort contained in the technical proposal. As a part of its cost proposal, the offeror shall submit the information outlined below, together with supporting breakdowns. All direct costs (labor, material, travel, computer, etc.) as well as labor and overhead rates should be provided by contractor fiscal year (CFY). Detailed cost element breakdowns by Government Fiscal Year or calendar year are not required but may be requested. A one-page cost summary must be included unless the CALL specifically waives it. The supporting schedules may include summary level estimating rationale used to generate the proposed costs. The cost element breakdown should include the following if applicable.

a. Direct Labor: Direct labor should be detailed by number of labor hours by category of labor.

b. Labor and Overhead Rates: Direct labor hours, with their applicable rates, must be broken out and the bases used clearly identified. The source of labor and overhead rates and all pricing factors should be identified. For instance, if a Forward Pricing Rate Agreement (FPRA) is in existence, that should be noted, along with the Administrative Contracting Officer’s (ACO's) name and telephone number. If the rates are based on current experience in your organization, provide the historical base used and clearly identify all escalation, by year, applied to derive the proposed rates. If computer usage is determined by a rate, identify the basis used and rationale used to derive the rate.

c. Material/Equipment: List all material/equipment items by type and kind with associated costs and advise if the costs are based on vendor quotes, data and/or engineering estimates;

provide copies of vendor quotes and/or catalog pricing data.

d. Subcontractor Costs: Submit all subcontractor proposals and analyses with your cost proposal (See FAR 15.404-3(b)). If the subcontractor will not submit cost and pricing information to the offeror, this information must be submitted directly to the Government for analysis. On all subcontracts and interdivisional transfers, provide the method of selection used to determine the subcontractor and the proposed contract type of each subcontract. An explanation shall be provided if the offeror proposes a different amount than that quoted by the subcontractor. The offeror’s proposal must:

• Identify principal items/services to be subcontracted.

• Identify prospective subcontractors and the basis on which they were selected. If non-competitive, provide selected source justification.

• Identify the type of contractual business arrangement contemplated for the subcontract and provide rationale.

• Identify the basis for the subcontract costs (e.g., firm quote or engineering estimate, etc.)

• Identify the cost or pricing data submitted by the subcontractor.

• Provide an analysis of the proposed subcontract in accordance with FAR 15.404- 3(b).

• Provide an analysis concerning the reasonableness, realism and completeness of each subcontractor’s proposal. If the analysis is based on comparison with prior prices, identify the basis on which the prior prices were determined to be reasonable. The analysis should include, but not be limited to, an analysis of:

materials, labor, travel, other direct costs and proposed profit or fee rates.

e. Special Tooling or Test Equipment: When special tooling, and/or test equipment is proposed, attach a brief description of items and indicate if they are solely for the performance of this particular contract or project and if they are or are not already available in the offeror's existing facilities. Indicate quantities, unit prices, whether items are to be purchased or fabricated, whether items are of a severable nature and the basis of the price.

These items may be included under Direct Material in the summary format.

f. Consultants: When consultants are proposed to be used in the performance of the contract, indicate the specific project or area in which such services are to be used. Identify each consultant, number of hours or days to be used and the consultant's rate per hour or day.

State the basis of said rate and give your analysis of the acceptability of the consultant's rate.

g. Travel: Travel costs must be justified and related to the needs of the project. Identify the number of trips, the destination and purpose. Travel costs should be broken out by trip with number of travelers, airfare, per diem, lodging, etc.

h. Computer Use: Detail the amount and kind of computer usage, the cost, and how the costs were derived.

i. Facilities Capital Cost of Money: If Facilities Capital Cost of Money is proposed, a properly executed DD Form 1861 is required.

j. Project Funding Profile: Offerors should include a project funding profile by Government

Fiscal Year (GFY) (1 Oct through 30 Sept) for budgetary purposes. This will enable the Government to easily identify program funding needs by GFY.

k. If an offeror takes exceptions to the requirements called out in the announcement (e.g., base support, GFP, CDRLs), the exceptions should be clearly stated in the cost proposal.

l. Forward Pricing Rate Agreements: Offerors who have forward pricing rate agreements (FPRA’s) and forward pricing rate recommendations (FPRR’s) should submit them with their proposal.

m. Cost/Business proposals have no page/formatting limitations.

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

4.5. Proposal - Peer or Scientific Review Criteria: Proposals will be reviewed against the criteria listed below.

The technical aspect, which is ranked as the 1st (first) order of priority, shall be reviewed based on the following criteria in DESCENDING order of importance:

1st - Technical:

(a) 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.

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

(c) 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.

(d) 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.

2nd - Cost/Price:

The cost evaluation includes the realism of the proposed cost. Cost/Price is a substantial factor but ranked as the 2nd (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).

4.6. Proposal - Review and Selection Process

4.6.1. 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 evaluation, as well as importance to agency programs and funding availability.

• Selectable: Proposals are recommended for acceptance if sufficient funding is available.

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

4.6.2. No other evaluation criteria will be used. 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 as Selectable, though the proposal as a whole, may not merit such a categorization.

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

4.6.4. Additional terms, conditions, and instructions applicable to the CALL –

4.6.5. Section K: A completed Section K will be required to be completed.

4.6.6. Model Contract: The BAA contains a model contract as an example only. Applicable Clauses, terms, and conditions may vary per contractor and per proposal and will be addressed during potential negotiations.

4.7. Award Administration Information:

4.7.1. Award Notices: Offerors will be notified whether their proposal (i.e., in response to a CALL) is recommended for award by e-mail. The notification is not to be construed to mean the award of a contract is assured, as availability of funds and if necessary, successful negotiations are prerequisites to any award.

4.7.2. Administrative and National Policy Requirements: See Section I in Revised BAA 5 June 2024 (page 4).

4.7.3. Reporting: Refer to paragraph Section I in Revised BAA 5 June 2024 CDRLs.

5. ADDITIONAL INFORMATION:

5.1. 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 Proposals shall be in accordance with the BAA, unless deviations are authorized in this CALL.

5.2. 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.

5.3. Security Risk Review:

The Security Risk Review is applied to federally funded research designed to help protect Department of the Air Force Science and Technology (S&T) by identifying possible vectors of undue foreign influence. AFRL will follow all policy and procedures outlined in Air Force Research Laboratory (AFRL) Instruction AFRLI 61- 113, Science and Technology Protection for the Air Force Research Laboratory and Department of the Air Force Instruction DAFI 63-101/20-101, Integrated Lifecycle Management.

(a) Security risk review for these subject application/proposals will be developed for all proposed Senior/Key personnel and “Covered Individuals”. These risk reviews will be based on information disclosed in a Research and Related Senior and Key Person Profile and Security Questionnaire. In addition, any accompanying or referenced documents, publicly available information, and information contained in internal U.S. Government databases will be utilized in risk reviews.

Nationality or citizenship is not a factor in the security risk reviews.

(b) When considering all external engagements, AFRL incorporates a holistic decision-making process that encompasses technical and security factors. The security review method implemented by AFRL measures risk factors to identify the appropriate Risk Acceptance Level (RAL) within the organization. The objective analysis of the security risk factors is conducted to empower AFRL’s S&T leaders to make risk-informed decisions. The review process generally looks at five factors, or risk areas, but with authority for expanded review as noted in OSD R&E Memorandum dated 6 Jun 2023. The potential security risk factors are set forth below:

Potential security risk factors:

5.3.1 Actions Required by Applicants/Recipients and/or Offerors/Contractors at application/proposal submission. In accordance with AFRLI 61-113, S&T Protection, Applicants/Recipients and/or Offerors/Contractors are required to submit the following documentation with their application/proposal:

(a) Contract or Other Transaction Agreement (OTA) proposals:

(i) Research and Related Senior and Key Person Profile Worksheet (See Appendix 3) AND;

(ii) Security Program Questionnaire (See Appendix 2) AND;

(iii) “Privacy Act Statement” consent form for each Covered Individual that is also signed by the Applicant/Recipient as that Individual’s Sponsor. (See “Covered Individual” section below, and Appendix 4)

(b) In the event a security risk is identified, and the Government has determined the security risk exceeds the acceptable threshold, the Applicant/Recipient and/or Offeror/Contractor will be notified and informed of the decline of award. The Government will provide as much rationale for the decision as Government OPSEC measures allow for. Challenges under awards made solely for Fundamental Research shall follow the OSD R&E Memorandum dated 6 June 2023. Challenges under any other type of award shall follow the Ombudsman procedures within this Announcement/Solicitation.

(c) By submission of the Research and Related Senior Key Person Profile and Security Program Questionnaire, the Applicant/Recipient and/or Offeror/Contractor agrees to comply with the following:

(i) To certify that each covered individual who is listed on the application has been made aware: 1) of all relevant disclosure requirements, including the requirements of 42 U.S.C. § 6605; and 2) that false representations may be subject to prosecution and liability pursuant to, but not limited to, 18 U.S.C. §§287, 1001, 1031 and 31 U.S.C. §§ 3729-3733 and 3802. See National Science and Technology Council Guidance for Implementing National Security Presidential Memorandum 33 (NSPM-33) on National Security Strategy for United States Government-Supported Research and Development (January 2022).

(ii) To establish and maintain an internal process or procedure to address foreign talent programs, conflicts of commitment, conflicts of interest, and research integrity.

(iii) To exercise due diligence to identify Foreign Components or participation by Senior/Key Personnel in Foreign Government Talent Recruitment Programs and agree to share such information with the Government upon request.

5.3.2 Actions Required by Covered Individuals.

(a) Covered Individual. An individual who contributes to a substantive, meaningful way to the scientific development or execution of a research and development project proposed to be carried out with a research and development award from a federal research agency; and is designated as a covered individual by the federal research agency concerned. See 42 U.S.C. § 6605, Definitions. (Note: For purposes of a Broad Agency Announcement (BAA) solicitation, “covered individuals” are all Senior/Key Personnel.)

(b) Federal law requires that all current and pending research…