Attachment 1 CHEERS Industry Guide Amend 01_20Nov2025.pdf

Continuing Human Enabling, Enhancing, Restoring, and Sustaining

(CHEERS)

Multiple Authority Announcement (MAA)

Industry Guide

Version 2.0

Air Force Research Laboratory

Human Effectiveness Directorate & the United States Air Force School of Aerospace Medicine

(AFRL/RH & USAFSAM)

20 November 2025

Contents

CHAPTER 1: INTRODUCTION

CHAPTER 2: MAA SOLICITATION VARIATIONS

CHAPTER 3: GENERAL SOLICIATION PROCESS

CHAPTER 4: WHITE PAPER/PROPOSAL PREPARATION INSTRUCTIONS

CHAPTER 5: REVIEW AND SELECTION PROCEDURES

CHAPTER 6: ADDITIONAL FAR-BASED REQUIREMENTS

CHAPTER 7: ADDITIONAL ASSISTANCE INSTRUMENT REQUIREMENTS

CHAPTER 8: ADDITIONAL REQUIREMENTS FOR OTHER TRANSACTIONS (OTs) UNDER 10 USC §4021, §4022, and §4023

CHAPTER 1: INTRODUCTION

1. MAA Overview: A Multiple Authority Announcement (MAA) is a unique solicitation method in which various solicitation authorities are consolidated under a single announcement. The CHEERS MAA is intended to provide a comprehensive strategy for the Air Force Research Laboratory, Human Effectiveness Directorate and the United States Air Force School of Aerospace Medicine’s (AFRL/RH and USAFSAM) range of Science and Technology (S&T) and Studies and Analysis (S&A), by creating an announcement that allows for progression from basic research to technology maturation and transition.

This MAA may utilize Calls for Proposal and/or Open Period solicitations that enable study efforts on novel concepts, as well as R&D to mature technologies and conduct integrated demonstrations, experimentation, and eventual transition of technology to mission partners. Under this approach, individual Call for Proposal solicitations will be issued when requirements are identified by AFRL/RH or USAFSAM. Open Period solicitations will be issued when either AFRL/RH or USAFSAM wishes to receive offeror-generated ideas. Either solicitation type may utilize a one-step approach or a two-step approach. See Chapter 2 of this guide for more information on the available variations and formats of MAA solicitations.

To preserve the integrity of competition, a “moratorium” on White Paper acceptance under Open Period solicitations will be issued in cases where a Call for Proposal is released covering the same topic areas as the Open Period. The Open Period Moratorium will last 6 months and go into effect upon the closing date for proposal receipt under the Call for Proposals.

2. Using this Guide: This guide is intended to familiarize existing and potential

AFRL/RH or USAFSAM Industry Partners with the Multiple Authority Announcement (MAA) acquisition approach, as well as the specific nuances of the CHEERS MAA (referred to hereafter as “MAA” or “the Announcement”). This guide will:

Supplement information contained in the MAA and resulting solicitations.

Provide standardization which potential offerors can leverage to aid in streamlining their internal proposal preparation processes.

Reduce barriers to competition by providing supplemental information on less-familiar acquisition concepts/tools that are available for use, such as Other Transaction Authorities.

The Announcement and this Industry Guide will be reviewed and updated annually to ensure documents are reflective of the most current statutes, regulations and policy.

Potential offerors are encouraged to, first, become familiar with the MAA and this guide, and then use them for reference when responding to requirements released under solicitations. In the event of conflicting information, offerors should use the following order of precedence: (1) Solicitation; (2) MAA; (3) Industry Guide.

3. Solicitation Authority Limitations:

• BAA Authority (10 USC §4001/FAR Part 35) will be limited to 6.1 – 6.4 R&D funds

IAW DFARS 235.016 & be utilized for acquisition of basic and applied research and that part of development not related to the development of a specific system or hardware procurement. *Unless conditions in DFARS 235.006-71(b) are met.

• Commercial Solutions Opening Authority (10 USC §3458/DFARS Part 212) will be limited to the uses described in DFARS 212.7002.

• Other Transactions for Research Authority (10 USC §4021) can be either acquisition OR assistance. Will be limited to basic, applied, and advanced research projects.

• Other Transactions for Prototype Authority (10 USC §4022) will be limited to prototype projects that are directly relevant to enhancing the mission effectiveness of military personnel to be acquired or developed by DoD, or to improvement of platforms, systems, components, or materials in use by the armed forces.

• Procurement for Experimental Purposes Authority (10 USC §4023) will be limited to procurement for experiment or test purposes in the development of the best supplies that are needed for the national defense in the specified technical areas.

• Assistance Authority (10 USC §4001/32 CFR 22.205) will be limited to when the goal of the project is to provide assistance by transferring a thing of value to accomplish a public purpose.

4. Maximizing Competition Under CHEERS: The CHEERS MAA is designed to reach the broadest range of Industry Partners possible, including both Small and Large Businesses, Educational/Research Institutions and Non-Profit Organizations, as well as Non-Traditional Defense Contractors (NTDCs).

The CHEERS MAA will be posted on the Government Point of Entry (GPE), www.sam.gov, as a “Special Notice”. Individual solicitations issued under the CHEERS MAA will be posted as stand-alone “Solicitations” and will include a link to the MAA posting.

Solicitations issued under the authority of 32 CFR 22.205, will also be posted on www.grants.gov. All information that a potential offeror might need to respond to a solicitation, will be posted with the solicitation. However, offerors may find it helpful to refer back to the original MAA posting and amendments. The MAA posting and individual solicitation postings are intentionally kept separate in order to reduce potential digital congestion.

Offerors interested in specific Technical Areas are encouraged to review the CHEERS Solicitation Log excel spreadsheet located at the Announcement posting on www.sam.gov (reference Special Notice posting). This spreadsheet can be sorted by Technical Area to identify all solicitations that have released requirements in that area. Potential offerors are also encouraged to “follow” the CHEERS MAA and subsequent solicitations. Offerors can follow a solicitation by hitting the “Follow” button in the upper right corner of the posting.

http://www.sam.gov/ http://www.grants.gov/ http://www.sam.gov/

CHAPTER 2: MAA SOLICITATION VARIATIONS

The following solicitation variations are approved for use under this MAA. A single solicitation may use one or any combination of the following:

1. Call for Proposal: One- or two-step requests for proposal that allow for submittal at a defined date and time as specified in the solicitation. Adequate Price Competition may exist.

2. Open Period: One- or two-step requests for proposal that allow for submittal at any time within the active period specified in the solicitation. Open Period solicitations provide maximum adaptability for both Government and Industry to account for ever changing/evolving technology landscape and/or when contractor-generated ideas are sought. Adequate Price Competition will not exist.

The above solicitation variations may be issued in either of the following formats. Refer to Chapter 4 of this User Guide for more specific requirements for each format:

1. One-Step: Potential offerors are invited to submit a full Cost and Technical Proposal in response to, and in accordance with, the requirements established in this MAA and the applicable solicitation.

2. Two-Step: Potential offerors are invited to submit a White Paper in response to, and in accordance with, the requirements established in this MAA and the applicable solicitation. Full technical and cost proposals will then be requested from those offerors who submitted White Papers determined to be of further interest to AFRL/RH or

USAFSAM.

CHAPTER 3: GENERAL SOLICIATION PROCESS

1. Solicitations under CHEERS – either Calls for Proposal OR Open Periods – will be announced on the Government Point of Entry (GPE) (www.sam.gov) and, for solicitations that contemplate the use of Assistance Instruments, www.grants.gov. Solicitations will request interested offerors to submit either a White Paper (Two-Step process) or full Technical and Cost Proposals (One- Step process). It is recommended that interested Offerors read each Solicitation very carefully. Solicitation information may vary, but will likely include the following:

An identifying Individual Solicitation Title and Number Applicable Solicitation Authority Applicable MAA Technical Area(s) Statement of Objectives (SOO) or Research Objectives or Research Problem Statement of Work (SOW) Supplemental Requirements Technical and Contracting Points of Contact Anticipated Deliverable Items, including any anticipated hardware, software, or data deliverables Program Security Classification/TEMPEST Requirements Specific export-control requirements. If export controlled technical data is involved, a note advising that only firms holding certification under the US/Canada Joint Certification Program (JCP) are allowed access to such data.

Science & Technology (S&T) Protection Requirements Government Furnished Property (GFP) Requirements White Paper/Proposal Due Date & Time Base Support/Network Access Anticipated Contract Type(s)/Instrument(s) Data Rights Desired Anticipated Award Dates and Funding Information White Paper/Proposal format, if deviates from Industry Guide Evaluation Criteria for White Paper/Proposals, if deviates from MAA Additional Administrative and National Policy Requirements not already identified Reporting requirements Section K, Representations and Certifications attachment

2. AFRL/RH or USAFSAM reserves the right to award zero, one, or more contracts for all, some or none of the solicited effort based on the offeror’s ability to perform desired work and funding fluctuations.

3. Data Rights Desired: It is anticipated that solicitations issued under this MAA will be primarily for Research and Development efforts where AFRL/RH or USAFSAM anticipates funding the development of the data. The following outlines the most anticipated data rights desired. Any expected deviations will be identified in the solicitation. The FAR(S) clauses referenced below do not apply to awards made pursuant to Non-FAR authorities, however those efforts are expected to utilize the following framework as a starting point for negotiations.

http://www.grants.gov/

(1) Other Than Commercial Technical Data: Unlimited Rights

(2) Other Than Commercial Computer Software: Unlimited Rights

(3) Other Than Commercial Software Documentation: Unlimited Rights

(4) Commercial Computer Software Rights: Customary Commercial License consistent with Federal statutes and regulations

Terms used in this section are defined in the clauses at 252.227-7013, Rights in Technical Data-Other Than Commercial Products and Commercial Services, and 252.227-7014, Rights in Other Than Commercial Computer Software and Other Than Commercial Computer Software Documentation.

Offerors that propose delivery of other than commercial technical data, other than commercial computer software, or other than commercial computer software documentation subject to less than Unlimited Rights should fully explain how a portion or all of the data was developed at private expense. Specifically, offerors must explain what other than commercial technical data, other than commercial computer software, or other than commercial computer software 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 shall include the data rights assertions as required by DFARS 252.227- 7017, Identification and Assertion of Use, Release, or Disclosure Restrictions. The data rights assertions list is included in Section K (an attachment to the solicitation) and is due by the proposal due date listed within the solicitation. Assertions must be completed with specificity. Each assertion must identify the other than commercial technical data or computer software to be delivered and the associated item, component, process, software, or documentation developed exclusively or partially at private expense to which it pertains. Nonconforming data rights assertions will be returned until the table complies with DFARS 252.227-7017.

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

a. Third Party Software (Commercial and Other Than Commercial): In accordance with DFARS 252.227-7014(d), 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.

If any such software, other than commercial 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 and performance.

b. Other Than Commercial Computer Software: All other than commercial computer software will receive the appropriate level rights set forth in DFARS 252.227-7014(b). Which include: Unlimited rights, Government Purpose Rights (GPR), Restricted Rights, or rights identified within a specifically negotiated license attached to the contract.

DFARS 252.227-7014(d) describes requirements for incorporation of third party other than commercial copyrighted computer software or computer software documentation.

The following may be applicable to any solicitations in which any amount of commercial computer software is anticipated to be delivered under a resulting award.

End User License Agreement (EULA), Software Terms of Service (TOS), or similar legal instrument or agreement - There are common commercial software license terms within EULA, TOS, or similar legal instruments or agreements that violate Federal law and therefore shall not be included or incorporated under any awards made against this MAA. If the proposed offer includes any of these type of instruments or agreements, the offeror is required to provide a signed software license rider along with its proposal. The software license and rider will be attached to the awarded action. The Contracting POC identified in the solicitation can provide a copy of the Rider template, as necessary.

The following is a non-exhaustive list of terms and conditions which are inconsistent with Federal law or Government policy and shall not be included in the commercial computer software license agreement between the Licensor and the Government. Only the Contracting Officer has the authority to bind 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.

9) The license shall not hold the Government liable for directly imposed sales and use taxes.

Additionally, the Contractor may be required to obtain licenses that comply with any or all of the following terms and conditions, as applicable, based on the Government’s needs:

1) The license shall not disclaim all warranties through use of an “as is” provision.

2) 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) 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) 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:

a) Contract Line Item Numbers (CLINs);

b) Contract Deliverables (CDRLs);

c) Paragraphs in the Statement of Work (SOW); and

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

4. Government Furnished Property (GFP) Availability: Solicitations will identify if any GFP is anticipated to be available for use during performance. 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.

If an offeror proposes the use of GFP, other than GFP identified in the solicitation, the offer must specifically identify each piece of GFP in the Cost/Business Proposal and propose and substantiate a rental cost for evaluation purposes. 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.

5. Science & Technology (S&T) Protection

a. Security Risk Review

1) 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.

2) Security risk review for 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.

3) 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 The Office of the Under Secretary of Defense for Research and Engineering (OUSD (R&E)) Memorandum dated 6 Jun 2023. The potential security risk factors are set forth below:

4) The documents identified in the ensuing sections are provided as Appendices to the CHEERS MAA and are further discussed in Chapters 4 and 7 of this Guide.

b. Actions Required by Offerors at Proposal Submission

1) By submission of the Research and Related Senior Key Person Profile and Security

Program Questionnaire, the Offeror 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.

c. Actions Required by Covered Individuals

1) 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.)

2) Federal law requires that all current and pending research support, as defined by 42 U.S.C. §6605, must be disclosed at the time of application/proposal submission, for all covered individuals. The Government may require an updated disclosure during the performance of any research project selected for funding. The Government will require an updated disclosure whenever covered individuals are added or identified as performing under the funded project.

3) Covered Individuals are also required to sign the “Privacy Act Statement” and provide such signed statement to the Applicant/Recipient and/or Offeror/Contractor for submission with the application/proposal.

4) Any decision to accept an application/proposal for funding under the solicitation will include full reliance on the individual’s statements. Failure to report fully and completely all sources of project support and outside positions and affiliations may be considered a material statement within the meaning of the False Claims Act, 31 U.S.C. 3729, and constitute a violation of Federal law.

d. Actions Required by Recipients/Contractors During Period of Performance

1) Re-submit the Research and Related Senior and Key Person Profile as an annual requirement. In addition, whenever a new Covered Individual(s) is to be added or identified as performing under the funded project, a new Research and Related Senior and Key Person Profile will be required prior to continued performance.

2) If, at any time, during performance the Recipient/Contractor learns that its Senior/Key Research Personnel (including any sub awardee personnel who receive this designation) are or are believed to be participants in a Foreign Government Talent Program or have Foreign Components with a strategic competitor or country with a history of targeting U.S. technology for unauthorized transfer, the Recipient/Contractor shall notify the Contracting/Grants/Agreements Officer within 5 business days of awareness.

i. This disclosure must include specific information as to the personnel involved and the nature of the situation and relationship. The Government will review this information and conduct any necessary fact-finding or discussion with the Recipient/Contractor. The Government’s determination on disclosure may include acceptance, mitigation, or termination of the award.

3) Failure of the Recipient/Contractor to reasonably exercise due diligence to discover or ensure that neither it nor any of its Senior/Key Research Personnel involved in the award are participating in a Foreign Government Talent Program or have a Foreign Component with a strategic competitor or country with a history of targeting U.S. technology for unauthorized transfer may result in the Government exercising remedies in accordance with federal law and regulation.

4) The Recipient/Contractor will be required to flow down this requirement to all sub awardees/contractors who have personnel designated as Senior/Key Research Personnel as a result of their involvement in the performance of the research.

6. Ombudsman

a. An ombudsman has been appointed to hear and facilitate the resolution of concerns from offerors, potential offerors, and others for this announcement/solicitation. When requested, the ombudsman will maintain strict confidentiality as to the source of the concern. The existence of the ombudsman does not affect the authority of the Program Manager or Contracting Officer. Further, the ombudsman does not participate in the evaluation of the proposals, or the adjudication of protests or formal contract disputes.

The ombudsman may refer the interested party to another official who can resolve the concern.

b. Before consulting with an ombudsman, interested parties must first address their concerns, issues, disagreements, and/or recommendations to the Contracting Officer for the resolution. Consulting an ombudsman does not alter or postpone the timelines for any other processes (e.g., agency level bid protests, GAO bid protests).

c. If resolution cannot be made by the Contracting Officer, the interested party may contact the ombudsman:

Ombudsman: AFRL/PK Technical Director Alternate Ombudsman: AFRL/PK Deputy Director of Contracting 1864 4th Street

WPAFB, OH 45433

Phone: (937) 503-2186 Email: afrl.pk.workflow@us.af.mil Concerns, issues, disagreements, and recommendations that cannot be resolved at the Center/MAJCOM/DRU/SMC ombudsman level may be brought by the interested party for further consideration to the Air Force ombudsman, Associate Deputy Assistant Secretary (ADAS) (Contracting), SAF/AQC, 1060 Air Force Pentagon, Washington DC 20330-1060, phone number (571) 256-3195, facsimile number (571) 256-2431.

d. The ombudsman has no authority to render a decision that binds the agency.

e. Do not contact the ombudsman to request copies of the announcement/solicitation, verify due dates, or clarify technical requirements/questions. Such inquiries shall be directed to the Contracting Officer.

mailto:afrl.pk.workflow@us.af.mil

CHAPTER 4: WHITE PAPER/PROPOSAL PREPARATION INSTRUCTIONS

1. Overview: Individual solicitations issued under CHEERS will identify whether a One- or Two-Step process is being utilized. Each individual solicitation will identify either a specified submission date OR the date in which a solicitation is considered closed and no more white papers/proposals will be accepted. Offeror’s responding to a One-Step Solicitation shall refer directly to the Proposal Preparation Instructions below. AFRL/RH or USAFSAM reserves the right to amend/modify any of the requirements below, based on the circumstances of individual solicitations. Any deviations will be clearly identified within the body of the solicitation. Potential offerors are reminded that in the event of conflicting information, offerors should use the following order of precedence: (1) Solicitation; (2) MAA; (3) Industry Guide.

2. The cost of preparing white papers or proposals in response to CHEERS solicitations 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.

3. Offerors are advised that only Contracting/Grants/Agreements Officers are legally authorized to contractually bind or otherwise commit the Government.

4. No classified white papers or proposals 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 for delivery instructions.

5. White Paper Preparation Instructions:

a. General: A Two-Step solicitation requests a white paper and rough order of magnitude (ROM) cost. The white paper shall include a discussion of the nature and scope of the offeror’s proposed technical approach and the way in which it aligns to the SOO.

AFRL/RH or USAFSAM will review the white papers in accordance with the FIRST STEP Peer or Scientific Review criteria, set forth in Chapter 5 below. Based on this review, AFRL/RH or USAFSAM will determine which of the white papers have the potential to best meet AFRL/RH or USAFSAM’s needs. Offerors will be notified of the disposition of their white paper. Those offerors submitting white papers assessed as meeting AFRL/RH or USAFSAM needs, will be asked to submit a technical and cost proposal. Those offerors not requested to submit a technical and cost proposal will not be further considered, but may request feedback information in accordance with Section 8.3 of the MAA. An offeror submitting a proposal without first submitting a white paper will not be eligible for an award.

b. Page Limitation:

1) The White Paper shall be limited to 5 pages, prepared and submitted in Word format.

2) Font shall be standard 10-point business font Arial.

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

4) 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.

5) 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.

6) 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, etc. AFRL/RH or USAFSAM will not consider pages in excess of these limitations.

c. Format: The white paper will be formatted as follows:

1) Section A: Solicitation Number (Note: this is the solicitation number, not the CHEERS MAA announcement number FA2384-24-S-2233), Title of Program, Name of Offeror, Business Size, Commercial and Government Entity (CAGE) number, Unique Entity Identifier (UEI) number, Offeror’s Contracting POC and Technical POC names telephone numbers and email addresses.

Solicitations requesting classified submissions may require the following information: Classified level at which submitter is cleared, submitter 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)). The ROM shall be formatted to provide both annual and total costs. Major tasks shall be separately estimated.

d. Technical Portion: The technical portion of the white paper shall include a discussion of the nature and scope of the effort and the offeror’s proposed technical approach/solution.

It may also include any proposed deliverables. Resumes, descriptions of facilities and equipment, a proposed Statement of Work are not required at this point.

e. Cost Portion: No detailed price or cost support information should be forwarded; only a time-phased bottom line ROM should be provided.

f. Other Information: If the offeror wishes to restrict a white paper, they must be marked with the restrictive language stated in FAR 52.215-1(e). See Sec 6(b) for additional information.

g. White Paper/Proposal Content Summary: You may be ineligible for award if all requirements of the CHEERS MAA and applicable solicitation are not met on the White Paper due date.

6. Proposal Preparation Instructions:

a. General: If utilizing a one-step solicitation, AFRL/RH or USAFSAM will request submission of a technical and cost proposal directly from offerors. If utilizing a two-step solicitation, offerors will be directed to submit a technical and cost proposal via issuance of a Request for Proposal (RFP). The RFP will explicitly state the due date for proposal.

Offerors can expect roughly 30 days for proposal turnaround, depending on scope of proposal effort. After receipt, proposals will be reviewed in accordance with the award criteria in Chapter 5 of this guide. Proposals will be categorized and subsequently selected for funding.

b. 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 online at:

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

This guide is specifically designed to assist the offeror in understanding the BAA proposal process, but is also applicable to other AFRL/RH or USAFSAM solicitation methods, including this CHEERS MAA.

c. Technical/management and cost/business volumes should be submitted in separate volumes and must be valid for 180 days.

d. Proposals must reference the Solicitation number.

e. Although NOT anticipated in most cases, solicitations will identify if offerors are required to submit HARD COPY proposals, in additional to electronic proposals. If required, specific delivery instructions and the number of copies required will be identified.

f. If a Solicitation indicates that an IDIQ type effort is anticipated, Offerors must propose each of the following to be considered for an IDIQ award:

1) Basic IDIQ Proposals

a) Basic IDIQ proposal-Technical and Management

b) Basic IDIQ Statement of Work (SOW) in response to applicable

Statement of Objectives (SOO)

c) Basic IDIQ Business Proposal (including Subcontracting Plan, if applicable, in accordance with FAR 19.7)

2) Task Order (TO) Proposals (required for every TO that the Offeror wishes to propose against)

a) T.O. Proposal-Technical and Management http://www.afrl.af.mil/Portals/90/Documents/HQ/BAA%20Ind%20Guide%202020.pdf

b) T.O. SOW in response to applicable SOO

c) T.O. Cost (TO only) and Business Proposal

7. Technical/Management Proposal Requirements:

a. Page Limitations:

1) The Technical/Management Proposal shall be limited to TBD per Solicitation or RFP pages. Technical/Management proposals and Statements of Work must be provided in Microsoft Word. Signed pages may be submitted in Adobe.

2) IDIQ Efforts: the Technical/Management Proposal shall be limited to TBD per Solicitation or RFP pages for the Basic IDIQ; and the Technical/Management Proposal shall be limited to TBD for each for TO.

3) Font shall be standard 10-point business font Arial.

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

5) 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.

6) 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.

7) Pages shall be numbered starting with the cover page being Page 1, and the last page being no greater than Page TBD. The page limitation covers all information including indices, photographs, foldouts (counted as 1 page for each 8.5 by 11 portion) tables, charts, appendices, etc.

8) 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 5 pages.

b. S&T Protection Required Documents: In accordance with AFRLI 61-113, Offerors are required to submit the following documentation with the proposal:

1) Security Program Questionnaire (MAA Appendix 2); AND

2) Research and Related (R&R) Senior and Key Person Profile Worksheet (MAA

Appendix 3); AND

3) “Privacy Act Statement” consent form for each Covered Individual that is also signed by the Offer as the Individual’s Sponsor (MAA Appendix 4). See also Chapter 3.

c. Please Note: AFRL/RH or USAFSAM 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.

d. 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 desired), 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 attachments will not count toward page count but should not be used as a way to circumvent page count limitations.

The Technical/Management proposal(s) shall include a SOW (in response to the AFRL generated SOO attached to each applicable solicitation issued under this MAA) detailing the technical tasks proposed to be accomplished under the proposed effort. Do not include any proprietary information in the SOW. In addition to the contractor proposed SOW, an AFRL/RH or USAFSAM generated SOW attachment containing additional contracting requirements will be included in any resulting contracts. An AFRL/RH or USAFSAM generated Statement of Objectives (SOO) will be attached to subsequent solicitations issued under this MAA.

8. Cost/Business Proposal:

a. Separate the proposal into a business section and cost section. If adequate price competition (APC) is anticipated for FAR-based contracts, that will be indicated in the solicitation. If APC does not exist, and the negotiated contract is equal to or expected to exceed the threshold identified in FAR 15.403-4, submission of certified cost or pricing data will be required.

b. The business section should contain all business information pertinent to the proposed contract, such as type of contract, any exceptions to terms and conditions of the announcement and/or solicitation (including any model contract, if provided with solicitation), any information not technically related, etc. Provide rationale for exception.

c. Associate Contractor Agreements (ACAs): If applicable, 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 FAR-based contracts, expected to exceed the threshold identified at FAR 19.702(a)(1)(i), 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 for FAR-based contracts.

g. Certifications and Representations (Section K): For FAR-based contracts, a completed Section K may due with the proposal. A Section K may be attached to solicitations issued under this MAA. Offerors may also be required to submit updated or supplemental Certifications and Representations based on the specifics of their proposal.

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

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

2) 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.

3) 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.

4) 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 AFRL/RH or USAFSAM 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:

i. Identify principal items/services to be subcontracted.

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

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

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

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

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

5) 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. Identify items that have a lead time 60 calendar days or more. These items may be included under Direct Material in the summary format.

6) 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.

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

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

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

10) 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 AFRL/RH or USAFSAM to easily identify program funding needs by GFY.

i. If an offeror takes exceptions to the requirements called out in the MAA or applicable

Solicitation (e.g., base support, Government-furnished property (GFP), CDRLs), the exceptions should be clearly stated in the cost proposal.

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

k. Cost/Business proposals have no page limitations.

l. Proposal Content Summary: You may be ineligible for award if all requirements of the MAA and applicable solicitation are not met on the due date or closing date.

CHAPTER 5: REVIEW AND SELECTION PROCEDURES

1…