META_OPEN_BAA.pdf

2-Step Broad Agency Announcement

Overview Information

To access hyperlinks from this electronic solicitation – Hit CTRL and click on the link.

NAICS Code: 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.

Federal Agency Name: Air Force Research Laboratory, Sensors Directorate, Multi-Domain Sensing Autonomy Division (AFRL/RYA)

Broad Agency Announcement Title: Multi-Sensor Exploitation for Tactical Autonomy (META)

Broad Agency Announcement Type: This is the Initial Announcement.

Broad Agency Announcement Number: FA8650-19-S-1943

Catalog of Federal Domestic Assistance (CFDA) Number(s): 12.800 AIR

FORCE DEFENSE RESEARCH SCIENCES PROGRAM

THIS WILL BE A TWO-STEP SOLICITATION:

First Step: WHITE PAPER DUE DATE AND TIME: The BAA is open and effective until 20 August 2024. White papers will be considered if received any time prior to 1400 local time on 20 August 2024. Only white papers are due at this time.

Second Step: PROPOSAL DUE DATE AND TIME: To be provided in the Requests for Proposals sent to offerors that submit White Papers considered to meet the needs of the Air Force.

NOTE: White Paper/proposal receipt after the due date and time shall be governed by the provisions of FAR 52.215-1(c)(3). It should be noted that this installation observes strict security procedures to enter the facility. These security procedures are NOT considered an interruption of normal Government processes, and proposals received after the above stated

The 2-Step Process reduces acquisition resources for both the Government and industry. It may be considered when a large number of proposals are anticipated or to determine if further Government interest is warranted. If further interest is not warranted, industry saves unnecessary bid and proposal costs and the Government saves review time.

date and time as a result of security delays will be considered “late.”

Furthermore, note that if offerors utilize commercial carriers in the delivery of proposals, they may not honor time-of-day delivery guarantees on military installations. Be advised, if the U.S. Postal Service is used, this building only receives U.S. Postal Mail twice a week and delivery by that means may not meet the proposal due date and time established herein. Early white paper/proposal submission is encouraged.

Submission: White Papers must be submitted to the Contracting Point of Contact (POC): Matthew Mayles, Contract Specialist, AFRL/RYKSR, (937) 713-9849, or Barry Kain, Contracting Officer, AFRL/RYKSR, (937) 713-9986, Postal Delivery Address: 2130 8th St., Bldg 45, Wright-Patterson AFB, OH 45433-7541.

Solicitation Request: Air Force Research Laboratory, Sensors Directorate, Multi- Domain Sensing Autonomy Division (AFRL/RYA), Wright-Patterson Air Force Base is soliciting white papers on the research effort described below.

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 BAA will generally be Cost Plus Fixed Fee (CPFF): Cost reimbursement contracts require successful offerors to have an accounting system considered adequate for tracking costs applicable to the contract.

Estimated Program Cost: The total program value is $48,000,000 with multiple awards with an estimating range from $300,000 to $8,000,000.

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

Brief Program Summary: META will be an Open BAA to address challenges that face the research, development, assessment, demonstration and transition of sensing autonomy technologies. The goal of this effort to investigate, study, explore, examine, inquire, exploit, advance and solve the areas of research described below which are very innovative, high risk, and fundamental to advance research projects which address some particular sensing autonomy challenge. This research effort covers all sensing autonomy technologies including modeling, simulation and analysis (MS&A); multi-domain, multi-sensor data management, collection, experimentation and phenomenology investigation; as well as learning technologies, algorithms and computing for knowledge and understanding. The effort is estimated to be 10% basic, 75% applied and 15% advanced research. The majority of the projected TRL’s for the various research efforts range from TRL 1 to TRL 4. In addition, while not included in the BAA Technical Objectives in Paragraph III below, there is a potential that this effort, which includes any contracts issued resulting from this BAA, may also include technical objectives for incidental Operations and Maintenance (O&M) work and funding and incidental Procurement work and funding.

Additional research objectives, goals, and aims include knowledge generation through information fusion and the application of machine/deep learning techniques to solve military problems. This includes developing new technologies to address challenges related to multi-domain sensing for strategic, operational and tactical autonomy. This research effort will provide techniques for behavioral/physical knowledge generation from multiple sensors, domains (Air, Space, Cyber), and information types to include modeling, simulation, algorithm development, assessment and experiments across multiple distributed, homogeneous and heterogeneous sensors. The knowledge generated will support and inform the Observe-Orient-Decide-Act (OODA) loop for strategic (system and intelligence preparation for missions), operational (mission planning) and tactical (mission execution) elements of a single integrated multi-domain battlespace. The timeliness of the generated knowledge determines its ability to contribute to a strategic (long-term) plan, e.g., ISR, or to a tactical (short-term) decision, e.g., Strike. This research will focus on technologies including fusion for understanding (using spatial diversity, frequency diversity, transmit and receive adaptivity and information source diversity), target phenomenology characterization, denied and difficult target prosecution, algorithm performance assessment, experimentation, sensing decision-making strategies, knowledge representation, sensing data and knowledge management, distributed processing and capabilities to inform/enable joint inference and control. This research effort shall also investigate the application of machine/deep learning techniques to accomplish knowledge generation (i.e., detections, tracks, IDs, patterns, behaviors, intents) through information fusion.

Machine learning (ML) can include traditional ML, deep learning, reinforcement learning, and other novel ML approaches. High performance computing (HPC) will be leveraged for data generation, modeling, simulation, algorithm development and performance assessment as appropriate.

Communication Between Prospective Offerors and Government Representatives: The acquisition team intends to manage communications in a manner best designed to facilitate the submittal of optimal proposals while not providing any unfair competitive advantages. Technical communications will be managed by the Project Engineer identified below. Technical questions may be addressed up to white paper submittal. Questions determined to provide a competitive advantage will be answered via FedBizOpps. Dialogue between prospective offerors and Government representatives is encouraged until submission of proposals. Discussions with any of the points of contact shall not constitute a commitment by the Government to subsequently fund or award any proposed effort. Only Contracting Officers are legally authorized to commit the Government.

Address technical questions to the Technical POC: Cheutaunia Johnson, Project Engineer, AFRL/RYAP, (937) 713-8238, cheutaunia.johnson@us.af.mil.

Postal Delivery Address: 2241 Avionics Circle, Bldg 620, Wright-Patterson AFB, OH 45433-7333.

Address contracting questions to the Contracting POC: Matthew Mayles, Contract Specialist, AFRL/RYKSR, (937) 713-9849, matthew.mayles@us.af.mil, or Barry Kain, Contracting Officer, AFRL/RYKSR, (937) 713-9986, barry.kain@us.af.mil. Postal Delivery Address: 2130 8th St., Bldg 45, Wright- Patterson AFB, OH 45433-7541.

mailto:cheutaunia.johnson@us.af.mil mailto:matthew.mayles@us.af.mil mailto:barry.kain@us.af.mil

Full Text Announcement

I. Program Description: Air Force Research Laboratory, Sensors Directorate, Multi-Domain Sensing Autonomy Division (AFRL/RYA) is soliciting white papers (and later technical and cost proposals) on the following research effort:

1. Statement of Objective/Description of Technical Area(s): The complete Statement of Objective (SOO) is Attachment 7 to this BAA.

2. Within Scope Modifications: 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.

3. Deliverable Items:

a. Data Items: See attached DD Form 1423-1 Contract Data Requirements

List (CDRLs) (Attachment 6).

b. Software: Software deliverables to be determined (TBD) based on proposal, if applicable. Software deliverables may include prototypes and related documentation, including executables and source code.

c. Hardware: Hardware deliverables to be determined (TBD) based on proposal, if applicable. Hardware deliverables may include prototypes and related documentation.

d. Residual Materials: As Required; test equipment and other materials procured under contract performance.

e. Other: Sensor Data from data collects.

4. Schedule:

a. Overall effort: Approximately 24 to 60 months period of performance per contract.

b. Data Items: Specified on individual CDRL(s).

c. Software: Software deliverables date to be determined (TBD), if applicable.

d. Hardware: Hardware deliverables date to be determined (TBD), if applicable.

e. Residual Materials: Residual Materials deliverables date to be determined

(TBD), if applicable.

f. Other: Other deliverables date to be determined (TBD), if applicable.

5. Other Requirements:

a. This announcement incorporates FAR and supplement provisions and clauses by reference. The full text of provisions and clauses can be found at http://farsite.hill.af.mil/.

b. Program Security Classification: This effort may require a Top Secret (TS) facility clearance and Top Secret (TS) safeguarding capability. A solicitation-ready DD254 is included as Attachment 5. If Top Secret (TS) Sensitive Compartmented Information (SCI) is proposed, it will be handled accordingly. If a DD254 is applicable, offerors must verify their Cognizant Security Office information is current with Defense Security Service (DSS) at www.dss.mil.

c. TEMPEST Requirements: TEMPEST requirements apply to the SCIF execution location. See Defense Federal Acquisition Regulation Supplement (DFARS) Clause 252.239-7000, Protection Against Compromising Emanations, dated 25 Jun 04, revised 10 Jan 08;

Intelligence Community (IC) Tech Spec-for ICD/ICS 705, Technical Specifications For Construction and Management of Sensitive Compartmented Information Facilities, version 1.4, dated September 28, 2017; Committee on National Security Systems Advisory Memorandum (CNSSAM) TEMPEST/01-13, Red/Black Installation Guidance, dated 17 Jan 14.

d. OPSEC: See attached SOO for OPSEC guidance.

e. Export Control: Information involved in this research effort may be subject to Export Control (International Traffic in Arms Regulation (ITAR) 22 CFR 120-131, or Export Administration Regulations (EAR) 15 CFR 710- 774). If effort may be subject to export control, then a Certified DD Form 2345, Militarily Critical Technical Data Agreement, will be required to be submitted with proposal.

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

6. Other Information:

a. Government Furnished Property (GFP) Availability: Government Furnished Property (GFP) is not anticipated but may be made available if the use is found in the best interest of the Government.

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.

b. Base Support/ Network Access: Base Support

(1) Available Base Facilities: Office and Laboratory Space and appropriate computational resources for use in Building 620 will be based on whether it is requested in a proposal submitted as part of the open BAA two step process.

http://farsite.hill.af.mil/ http://www.dss.mil/

c. Multiple awards subject to Fair Opportunity are not anticipated.

d. Data Rights Desired:

(1) Technical Data: Unlimited Rights

(2) Non-Commercial Software (NCS): Unlimited Rights

(3) NCS Documentation: Unlimited Rights

(4) Commercial Computer Software Rights: Customary License (if required)

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 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 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 exchange for paying for development of the data, the Government expects technical data, NCS, and NCS documentation developed entirely at Government expense to be delivered with Unlimited Rights.

Technical data, NCS, and NCS documentation developed with mixed funding are expected to be delivered with at least Government Purpose Rights. Offerors that propose delivery of technical data, NCS, or NCS documentation subject to Government Purpose Rights should fully explain how a portion of the data was developed at private expense. Specifically, offerors must explain what 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 non-commercial technical data with Limited Rights, NCS with Restricted Rights, or NCS documentation with Limited Rights will be considered. Proposals should fully explain what 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 assertions lists will be rejected.

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—

(1) Computer software, has provided a statement of the license rights obtained in a form acceptable to the Contracting Officer; or

(2) 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 terms and conditions, among others, should not be included in the terms and conditions of the commercial computer software license between the Licensor and the Government (Licensee):

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, as these provisions may constitute obligations in advance or in excess of an appropriation and may 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.

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

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.

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 require automatic updates or give Licensor the authority to unilaterally replace the software.

5. [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:

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.

II. Award Information

1. Anticipated Award Date: Award dates will vary. White papers will be accepted for review through 20 August 2024.

2. Anticipated funding for the program not per contract:

FY20 FY21 FY22 FY23 FY24 Total $9.6M $9.6M $9.6M $9.6M $9.6M $48M

This funding profile is an estimate only and not a contractual obligation for funding. All funding is subject to change due to Government discretion and availability. Potential offerors should be aware that due to unanticipated budget fluctuations funding in any or all areas may change with little or no notice.

III. Eligibility Information

1. Eligible Offeror: This is an unrestricted solicitation. Small businesses are encouraged to propose.

2. Cost Sharing or Matching: Cost Sharing is not required.

3. Federally Funded Research and Development Centers: The following guidance is provided for Federally Funded Research and Development Centers (FFRDCs) contemplating submitting a proposal, as either a prime or subcontractor. FAR 35.017-1(c)(4) prohibits an FFRDC from competing with any non-FFRDC concern in response to a Federal agency request for proposal for other than the operation of an FFRDC (with exceptions stated in DFARS 235.017-1(c)(4)). There is no regulation prohibiting an FFRDC from responding to a solicitation. However, the FFRDC’s sponsoring agency must first make a determination that the effort being proposed falls within the purpose, mission, general scope of effort, or special competency of the FFRDC, and that determination must be included in the FFRDC’s proposal. In addition, AFRL must make a determination that the work proposed would not place the FFRDC in direct competition with domestic private industry. Only after these determinations are made, would a determination be made concerning the FFRDC’s eligibility to receive an award.

4. Government Agencies: If a Government agency is interested in performing work, contact the Program Manager identified in the BAA. If those discussions result in a mutual interest to pursue your agency's participation, the effort will be pursued independent of this announcement.

5. Other:

a. Foreign Participation: Foreign participation is not authorized at the prime contractor level. DoD solicitation provisions for 22 CFR 120-130 and 15 CFR 730-799 apply. Only U.S. persons are eligible for award. Use of non U.S. persons by the contractor, including subcontract arrangements, are subject to the aforementioned statutes.

b. This acquisition involves data that are subject to export control laws and regulations. Only contractors who are registered and certified with the Defense Logistics Services Center (DLSC) and have a legitimate business purpose may participate in this solicitation. Contact the Defense Logistics Services Center, 74 Washington Avenue N., Battle Creek, Michigan 40917-3084 (1-800-352-3572) for further information on the certification process. You must submit a copy of your approved DD Form 2345, Militarily Critical Technical Data Agreement, with your proposal.

c. There are no limits on the number of white papers/proposals an offeror may submit.

d. You may be ineligible for award if all requirements of this solicitation are not met on the white paper (and later proposal) due date as identified above.

http://www.dlis.dla.mil/jcp/

IV. White Paper / Proposal and Submission Information

1. Overview: This Announcement consists of a Two-Step Process described in detail below. White Papers/Proposals submitted shall be in accordance with this announcement. There will be no other solicitation issued in regard to this requirement. The Government intends to review white papers/proposals and award some, all, or none of the proposals received without negotiation/discussion; however, the Government reserves the right to negotiate with those offeror(s) whose proposal is selected for funding.

ONLY WHITE PAPERS ARE BEING SOLICITED AT THIS TIME.

Offerors should be alert for any BAA amendments that may permit extensions to the white paper submission date.

For additional information, a copy of the Broad Agency Announcement (BAA) Guide for Industry is located at http://www.wpafb.af.mil/Portals/60/documents/afrl/AFRL-broad-agency-announcement-guide.pdf?

2. First Step (White Paper) Instructions:

a. General: The FIRST STEP requests a white paper and a rough order of magnitude (ROM) cost. The white paper shall include a discussion of the nature and scope of the research and the offeror’s proposed technical approach. The Government will review the white papers in accordance with the FIRST STEP Peer or Scientific Review criteria, set forth in Section V below. Based on this review, the Government will determine which of them have the potential to best meet the Air Force’s needs. Offerors will be notified of the disposition of their white paper. It is anticipated that Government review of the white papers submitted will take 30 working days. Those offerors submitting white papers assessed as meeting Air Force needs will be asked to submit a technical and cost proposal. Those offerors not requested to submit a technical and cost proposal will be notified but may, however, still elect to submit a technical and cost proposal. An offeror submitting a proposal without first submitting a white paper will not be eligible for an award. The cost of preparing white papers in response to this Solicitation 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.

b. Page Limitation: The White Paper shall be limited to 7 pages, prepared and submitted in Word format. Font shall be standard 10-point business font Arial. Character spacing must be “normal,” not condensed in any manner. Pages shall be double-spaced (must use standard double-space http://www.wpafb.af.mil/Portals/60/documents/afrl/AFRL-broad-agency-announcement-guide.pdf 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. 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, and diagrams. These exceptions shall not be used to circumvent formatting requirements and page count limitations by including lengthy narratives in such items. Pages shall be numbered starting with the cover page being Page 1, and the last page being no greater than Page 7. The page limitation covers all information including indices, photographs, foldouts (counted as 1 page for each 8.5 by 11 portion) tables, charts, appendices, attachments, resumes, etc. The Government will not consider pages in excess of these limitations.

Offerors should submit 1 original and 2 hard copies of the White Paper via mail to the Contracting POC, identified in the Overview Information. Two

(2) CDs with the WORD version of your White Paper must be submitted with the hard copies of the White Paper, and must match the hard copy.

If there is a discrepancy between hard copies and electronic copies, the hard copies will take precedence.

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

(1) Section A: BAA Number, Title of Program, Name of Company, Business Size, Company’s Commercial and Government Entity (CAGE) number, Dun & Bradstreet (D&B) Data Universal Numbering System (DUNS) number, Contracting POC and Technical POC with appropriate telephone numbers, fax numbers, and email addresses for the POCs. Classified level at which company is cleared, contactor 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)).

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

e. Cost Portion: The cost portion of the white paper shall include a ROM cost estimate. No detailed price or cost support information should be forwarded; only a time-phased bottom line figure should be provided.

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

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

3. Second Step (Proposal) Instructions:

Note: If you intend to submit a proposal for an assistance instrument, go to Attachment 1 which discusses how to find the assistance opportunity, prepare the cover page, and complete the certification. This section also provides the process for electronic submission of proposals for assistance instruments that may be submitted in addition to BAA Section IV Paragraph 3.a.(5).

a. General Instructions:

(1) The SECOND STEP consists of offerors submitting a technical and cost proposal within 30 working days of the proposal request. After receipt, proposals will be reviewed in accordance with the award criteria in Section V. below. Proposals will be categorized and subsequently selected for negotiations.

(2) 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 http://www.wpafb.af.mil/Portals/60/documents/afrl/AFRL-broad-agency-announcement-guide.pdf. This guide is specifically designed to assist the offeror in understanding the BAA proposal process.

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

(4) Proposals must reference the announcement number FA8650-19-S- 1943 and relevant research area(s) from the Statement of Objectives (SOO), Attachment 7.

(5) Offerors must submit one-original and two hard copies of their proposals to the Contracting POC.

(6) Offerors must include 2 CDs in Microsoft Office or Adobe format containing all electronic versions of required submittals. All electronic versions must match the hard copies. If there is a discrepancy between hard copies and electronic copies, the hard copies will take precedence.

a) Technical/Management proposals, Statement of Work, and Subcontracting Plan (if Applicable in accordance with FAR 19.7) must be provided in Microsoft WORD. Signed pages may be submitted in Adobe.

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

c) The CDs should be labeled with the company name and proposal title.

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

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

(9) 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 for delivery instructions.

b. “C” Type contracts are the preferred contract type for this effort.

However, if an offeror chooses to propose an IDIQ type contract then they must propose/submit each of the following to be considered for an IDIQ award:

(1) Basic IDIQ

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 (T.O.) 0001 (and any additional T.O.)

a) T.O. 0001 Proposal-Technical and Management

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

c) T.O. 0001 Cost (T.O.s only) and Business Proposal

c. Technical/Management Proposal:

(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) If submitting an IDIQ proposal, the Technical/Management Proposal shall be limited to 25 pages for the Basic IDIQ; and the Technical/Management Proposal shall be limited to 25 pages each for T.O. 0001 and any additional T.O. with the pages, prepared and submitted in Microsoft Word format.

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

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

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

f) 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, and diagrams. These exceptions shall not be used to circumvent formatting requirements and page count limitations by including lengthy narratives in such items.

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

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

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

(2) 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. This volume 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 SOW Supplemental Requirements attachment containing additional contracting requirements will be included in any resulting contracts.

The SOW Supplemental Requirements attachment is included as Attachment 8 to this BAA.

http://www.afrl.af.mil/contract/default.htm http://www.afrl.af.mil/contract/default.htm

(3) Any questions concerning the technical proposal or SOW preparation shall be referred to the Technical POC.

d. Cost/Business Proposal:

(1) Separate the proposal into a business section and cost section.

a) See Attachment 2 for the Model Contract. Note that 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) The 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 $700,000, Subcontracting Plans shall be submitted in the cost/business proposal. Reference FAR 19.704, DFARS 219.704, and AFFARS 5319.704(a)(1) 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) can be found at Atch 3. Offerors may also be required to submit updated or supplemental Certifications and Representations based on the specifics of their proposal.

h) If an offeror proposes the use of Government Furnished Property (GFP), other than GFP identified in the BAA, 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:

(i) 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);

(ii) 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;

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

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

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

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

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, Government-furnished property (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 limitations.

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

3. Funding Restrictions: The cost of preparing proposals in response to this announcement is not considered an allowable direct charge to any resulting contract or any other contract, but may be an allowable expense to the normal bid and proposal indirect cost specified in FAR 31.205-18.

V. White Paper / Proposal Review Information

1. FIRST STEP – White Paper Peer or Scientific Review Criteria: The Government will review White Papers to determine which of them have the potential to best meet the Air Force’s needs based on the following criteria, which are listed in equal order of importance:

a. Is the technical approach consistent with the technologies listed in the

BAA?

b. Is the research of interest to the Government?

c. Is appropriate funding available?

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

a. Technical:

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

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

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

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

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