CATCH ARA Solicitation.pdf

Advanced Research Announcement (ARA) with Calls Overview Information

NAICS Code: The NAICS Code for this acquisition is 541715 and the small business size is 1,000 employees.

Federal Agency Name: Air Force Research Laboratory, AFRL/RY Sensors Directorate

ARA Title: Combat Identification Automated Target Recognition Technology (CATCH)

ARA Type: Initial Announcement

ARA Number: FA2377-25-R-B004

THIS IS AN ADVANCED RESEARCH ANNOUNCEMENT (ARA) THAT WILL

SOLICIT WHITE PAPERS/PROPOSALS THROUGH CALLS. THIS

ANNOUNCEMENT POSTS THE BASIC ARA AND DOES NOT REQUEST

SUBMITTALS AT THIS TIME. THE BASIC ARA WILL REMAIN OPEN FOR CALLS

UNTIL 14 March 2030.

Calls (One-Step or Two-Step, See Section IV for instructions):

Over the period of this ARA, calls may be issued to request white papers or proposals for specific area(s) of interest. It will be determined on a call by call basis whether or not the announcement is for white papers (two-step; requesting white papers, with potential to later request proposals) or proposals (one-step; requesting proposals).

Each call will contain specific requirements and pertinent information. White papers/proposals submitted in response to the calls will be accepted as specified in the individual calls and evaluated in accordance with the White Paper/Proposal Review Information (Section V1 and V2). Offerors should monitor the System for Award Management website at http://www.sam.gov in the event this announcement is amended or calls are issued.

White Paper/Proposal Due Date and Time:

ONE-STEP Call

• PROPOSAL DUE DATE AND TIME: To be determined (TBD) on individual calls.

TWO-STEP Call

• First Step: WHITE PAPER DUE DATE AND TIME - TBD on individual calls.

• Second Step: PROPOSAL DUE DATE AND TIME - To be provided in the “Requests for

Proposals (RFP)” sent to offerors whose white papers are considered to meet the needs of the Air Force (AF).

http://www.sam.gov/

NOTE: White Paper/proposal receipt after the due date and time shall be governed by the provisions of FAR 52.215-1(c)(3). Any white paper or proposal received at the Government office designated in this ARA after the exact time specified is “late” and will not be considered except at the Contracting Point of Contract’s discretion. 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 stated date and time in the call or Request for Proposal letter 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. Early white paper/proposal submission is encouraged.

Submission: White Papers and proposals must be submitted to the Contracting Point of Contact (POC): Joseph Mergler, Contract Negotiator, AFRL/RYKSR or Omar Eldadah, Contracting Officer, AFRL/RYKSR, Bldg. 45, 2130 8th St., WPAFB, OH 45433- 7541 or as otherwise indicated in the individual call.

Annual Updates: It is noted, for ease of reference, that this ARA will be republished at yearly intervals with required updates.

Solicitation Request: Air Force Research Laboratory, Sensors Directorate, Wright- Patterson Air Force Base is not soliciting white papers or proposals on the overarching effort described below. Individual calls, within scope of the ARA, will be issued that detail specific requirements. Unless otherwise stated in an individual call, all other requirements listed within this ARA are considered applicable.

Type of Contract/Instrument: The Air Force reserves the right to award contract(s) and/or Other Transaction(s) pursuant to 10 U.S.C. 4023 or 10 U.S.C 4022, based on the instrument deemed most appropriate. It is anticipated that contracts awarded under this ARA will generally be Cost Plus Fixed Fee (CPFF) or Cost type contracts.

NOTE: Cost reimbursable contracts require successful offerors to have an accounting system considered adequate by the Defense Contract Management Agency (DCMA) for tracking and costs applicable to the contract.

NOTE: If proposing a Federal Acquisition Regulation (FAR) based contract, the FAR clause references in this ARA shall apply. This announcement incorporates FAR and supplement provisions and clauses by reference. The full text of these provisions and clauses can be found at http://acquisition.gov. If proposing an Other Transaction (OT) these FAR references and clauses would not apply. The terms and conditions of an OT will be developed and negotiated on a case-by-case basis.

Estimated Program Cost: The total estimated program value is $95,000,000.00 with multiple awards ranging from $1,000,000.00 to $35,000,000.00 (the AF http://acquisition.gov/ reserves the right to exceed amounts if determined to be in the best interest of the Government).

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 Other Transactions and/or contracts, for all, some or none of the solicited effort based on the offeror’s ability to perform desired work and funding fluctuations.

There is no limit on the number of OTs or contracts that may be awarded to an individual offeror.

Brief Program Summary: This program completes work primarily ranging from TRL 3 to TRL 7 in modeling, simulation, and analysis (MS&A), technology development, integration, test and evaluation (T&E), and transition coordination. The program will look at the follow areas: (1) Sensor exploitation from multiple warfighting domains with focus on air, ground, and surface targets, (2) Exploitation and fusion of multiple sensor modalities, including active and passive modes, from single and multiple platforms,

(3) OMS technologies and third-party software and/or mode exploration

Communication Between Prospective Offerors and Government Representatives: Dialogue between prospective offerors and Government representatives is encouraged until submission of proposals. Technical communication will be managed by the technical POC listed below. Discussions with any of the POCs shall not constitute a commitment by the Government to subsequently fund or award any proposed effort. No guidance related to technical approach will be given. However, questions related to the objectives of the effort or prior similar efforts may be answered. Only Contracting Officers are legally authorized to commit the Government.

If there is any doubt as to whether a response provides a competitive advantage, the answer will be posted publicly via an amendment to this ARA on FBO. For offerors whose white papers are not selected to continue to proposal stage, notification and feedback will be managed by the Contracting POCs.

Address technical questions to the Technical POC:

Primary Technical POC Kameron Grubaugh, Program Manager, AFRL/RYZ

2241 Avionics Circle, WPAFB, OH 45433

(937) 713-8275 or Kameron.Grubaugh@us.af.mil mailto:joshua.mccamey@us.af.mil

Address contracting questions to the Contracting POCs:

Omar M. Eldadah, Contracting Officer, AFRL/RYKSR 2130 Eighth Street, Bldg. 45, WPAFB, OH 45433 omar.eldadah@us.af.mil

Joseph Mergler Contract Negotiator, AFRL/RYKSR 2130 Eighth Street, Bldg. 45, WPAFB, OH 45433 joseph.mergler@us.af.mil.

Full Text Announcement

I. Program Description: Air Force Research Laboratory, Sensors Directorate (AFRL/RYZ) is announcing its intent to solicit proposals under this “ARA with Calls”. Solicitations for white papers/proposals will be accomplished via calls. The calls will encompass the following effort:

II. Statement of Objective/Description of Technical Area(s):

The CATCH program will will look at the follow areas:

• Sensor exploitation from multiple warfighting domains with focus on air, ground, and surface targets

• Exploitation and fusion of multiple sensor modalities, including active and passive modes, from single and multiple platforms

• OMS technologies and third-party software and/or mode exploration

Calls issued against this ARA will:

• Develop and transition cutting-edge Combat Identification (CID) and fusion capabilities for single and multi-ship scenarios to encompass air, ground, and surface targets

• Operationalize, package, and transition essential CID enabling infrastructure while making critical enabling tools accessible to users without specialized knowledge of CID or signature prediction

• Increase CID relevance and transition opportunities beyond current 4th generation fighter platforms

• Establish a standardized, vendor-agnostic, and platform-independent database of single and multi-sensor CID features for ground and air targets

• Investigate innovative testing and demonstration approaches that increase CID relevance in a JADC2 environment

Calls to be issued against the CATCH ARA must a) fall under at least one of the Technical Areas of Interest detailed in paragraph I.1.a. below, and b) involve at least one of the tasks detailed in paragraph I.1.b. below.

a. Technical Areas of Interest:

1) Operationalization of Essential CID Enabling Technologies

2) Data Generation and Further CID R&D

3) All-Domain, All-Sensor Modality CID MS&A mailto:omar.eldadah@us.af.mil mailto:joseph.mergler@us.af.mil.

4) CID and Fusion Software and Algorithm Development

5) Hardware Development and Modification

6) Demonstration Test and Evaluation

7) System Maturation and Transition

b. Tasks

1) Develop a packaged tool for both air and ground targets which contains CAD models, signature predictors, and CID features

2) Create and transition realistic high-fidelity data sets using synthetic, measured, and commercial data, and develop a common CID feature database to reduce sustainment tails and increase CID performance

3) Evaluate anticipated technology performance improvements using AFSIM and custom engineering tools to understand impact at various modeling levels

4) Develop and enhance CID algorithms for single ship, multi-ship, and JADC2 capabilities, fusing multiple sensor modalities

5) Conduct testing (bench, SIL, HWIL, and flight) to increase technology readiness and prepare for integration

6) Mature capabilities to operational readiness by developing software updates, missionizing CID technologies, and updating databases and tools

1. 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 that may increase overall contract ceiling amount.

2. Deliverable Items:

a. Data Items: DD Form 1423-1 CDRLs will be utilized on contract awards.

Applicable data items will be identified in each call. OTs will specify data items on a case-by-case basis.

b. Software: Software deliverables are TBD per individual call, if applicable.

c. Hardware: Hardware deliverables are TBD per individual call, if applicable.

d. Other: TBD per individual call, if applicable.

3. Schedule:

a. Overall Period of Performance: TBD per individual call.

b. Data Items: TBD per individual call.

c. Software: TBD per individual call.

d. Hardware: TBD per individual call.

4. Other Requirements:

a. Program Security Classification: Anticipated up to a Top Secret Classification/ Safeguarding capability (including SCI, SAP/SAR), but security classification will be determined for each award. A draft DD254 will be attached to this ARA and will be attached to individual calls against the ARA as required. If a DD254 is applicable, offerors must verify their Cognizant Security Office information is current with Defense Security Service (DSS) at www.dss.mil.

b. OPSEC Requirements for Contracts: The implementation of General Operations Security (OPSEC) procedures, policies, and awareness is crucial to reducing program vulnerability from successful adversary collection and exploitation of critical information. OPSEC will be applied throughout the life cycle of the contract. To support this effort, the Critical Information and Indicators List (CIIL) and the RY OPSEC Plan will be provided by the AFRL/RYSP S&T Protection Office. By identifying and protecting Critical Information and Indicators (CII), the OPSEC process becomes a positive, proactive means by which adversaries are denied advantages. OPSEC is accomplished using a five-step process: 1) identification of CII; 2) threat analysis; 3) vulnerability analysis; 4) risk assessment; and 5) application of appropriate countermeasures. The contractor shall identify CII and develop and apply measures to mitigate risks. OPSEC strategies shall be documented in an OPSEC plan and delivered to AFRL after contract award.

While working on the government installation, the AFRL/RYSP S&T Protection Office will provide OPSEC guidance and training to ensure contractors are familiar with RY's CIIL and OPSEC Plan as it pertains to their contract. This training will be conducted in accordance with Air Force Instruction (AFI) 10- 701, Operations Security, and the Wright-Patterson Air Force Base (WPAFB) Supplement to AFI 10-701.

c. OPSEC Requirements for Assistance Agreements: The implementation of General Operations Security (OPSEC) procedures, policies, and awareness is crucial to reducing program vulnerability from successful adversary collection and exploitation of critical information. OPSEC will be applied throughout the life cycle of the contract. To support this effort, the Critical Information and Indicators List (CIIL) and the RY OPSEC Plan will be provided by the AFRL/RYSP S&T Protection Office. By identifying and protecting Critical Information and Indicators (CII), the OPSEC process becomes a positive, proactive means by which adversaries are denied advantages. OPSEC is accomplished using a five-step process: 1) identification of CII; 2) threat analysis; 3) vulnerability analysis; 4) risk assessment; and 5) application of appropriate countermeasures.

While working on the government installation, the AFRL/RYSP S&T Protection Office will provide OPSEC guidance and training to ensure contractors are familiar with RY's CIIL and OPSEC Plan as it pertains to their contract. This training will be conducted in accordance with Air Force Instruction (AFI) 10- 701, Operations Security, and the Wright-Patterson Air Force Base (WPAFB) Supplement to AFI 10-701.

d. Program Protection Plan (PPP): All DoD contractors (including subcontractors) shall supplement their current security practices by requiring any personnel involved in executing this contract where critical program information (CPI) has been identified to protect the CPI to the standards http://www.dss.mil/ articulated in the Program Protection Plan and in accordance with DoDI

5200.39. Upon contract award, all identified DoD contractors (including subcontractors) shall acknowledge and meet the requirements stated by the Program Manager for the protection of CPI. The DoD contractor must immediately notify the U.S. Government upon the discovery of any nonconformance with CPI protection.

e. Security Risk Review:

I. Notice of Intent.

(a) Security Risk Review. Each proposal submission will be subject to a Security Risk Review prior to selection for award. 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.

(b) Security risk review for these subject 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.

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

Potential security risk factors:

II. Actions Required by Applicants/Recipients at proposal submission.

(a) In accordance with AFRLI 61-113, S&T Protection, Applicants/Recipients are required to submit the following documentation with their proposal:

(1) Grant or Cooperative Agreement (CA) proposals:

(i) Standard Form 424, “Research and Related Senior and Key Person Profile (Expanded) (See Appendix 1) AND;

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

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

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

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

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

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

(3) In the event a security risk is identified, and the Government has determined the security risk exceeds the acceptable threshold, the Applicant/Recipient will be notified and informed of the decline of award. The Government will only provide a general statement of the reasoning due to Government OPSEC measures.

(4) By submission of the Research and Related Senior Key Person Profile and Security Program Questionnaire, the Applicant/Recipient 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.

III. Actions Required by Covered Individuals.

(a) Covered Individual. An individual who contributes to a substantive, meaningful way to the scientific development or execution of a research and development project proposed to be carried out with a research and development award from a federal research agency; and is designated as a covered individual by the federal research agency concerned. See 42 U.S.C. § 6605, Definitions. (Note:

For purposes of a Broad Agency Announcement (BAA) solicitation, “covered individuals” are all Senior/Key Personnel.)

(b) Federal law requires that all current and pending research support, as defined by 42 U.S.C. §6605, must be disclosed at the time of 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.

(c) Covered Individuals are also required to sign the “Privacy Act Statement” and provide such signed statement to the Applicant/Recipient for submission with the proposal. (See Appendix 4)

(d) Any decision to accept a proposal for funding under this announcement 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.

IV. Actions required by Applicants/Recipients during period of performance:

(a) Applicant/Recipient will be required to 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.

(b) If, at any time, during performance of this award, the Applicant/Recipient 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 Applicant/Recipient will notify the Contracting/Grants/Agreements Officer within 5 business days of awareness.

(c) 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 Applicant/Recipient. The Government’s determination on disclosure may include acceptance, mitigation, or termination of the award.

(d) Failure of the Applicant/Recipient to reasonably exercise due diligence to discover or ensure that neither it nor any of its Senior/Key Research Personnel involved in the subject 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.

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

f. Export Control: Information involved in this 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 is subject to export control, then a Certified DD Form 2345, Militarily Critical Technical Data Agreement, will be required to be submitted with proposal.

g. Export-Control Items: As prescribed by DFARS 225.7901-4, DFARS 252.225-7048, “Export Controlled Item (Jun 2013)” is contained in this solicitation. This clause (or similar language) shall be contained in ALL resulting awards.

h. Safety: The Contractor shall comply with all Air Force, federal, state, and local safety and environmental regulations. An approved safety plan in accordance with AFI 91-202 AFRL Supplement 1 shall be obtained before any experiment can be conducted at Wright-Patterson AFB and shall comply with all Air Force safety and environmental regulations. The contractor shall comply with system safety requirements contained in MIL-STD 882E, section 4, “General Requirements” for any deliverable systems or hardware and software interfaces with those components. The Contractor shall test and verify the safety-critical hardware and software for safety acceptance.

i. Contractor Performance Assessment Reporting System (CPARS):

Contractor Performance Assessment Reporting System (CPARS) will likely be applicable, but will be determined on a call by call basis in accordance with

FAR 42.1502 and DFARS 242.1502 (and CPARS Guide 2016, Section B, 2.0).

Interim and final evaluations of contractor performance for contract awards will be prepared in accordance with AFFARS 5342.1503. The final performance evaluation will be prepared at the time of completion of work. In addition to the final evaluation, interim evaluation(s) will be prepared annually. If an IDIQ contract is awarded as a result of a call, and CPARS will be conducted for each task order. Awardees will be requested to provide a POC to receive notifications of the opportunity to provide feedback. The contractor will be permitted 14 days to review the document and to submit additional information or a rebutting statement. If agreement cannot be reached between the parties, the matter will be referred to an individual one level above the Contracting Officer, whose decision will be final. Copies of the assessments, contractor responses, and review comments, if any, will be retained as part of the contract file, and may be used to support future award decisions for other procurements.

j. Overseas Performance: TBD per individual call/award.

k. Unique/Special Clauses: TBD per individual call/award.

l. Organizational Conflict of Interest (OCI): TBD per individual call/award.

m. Associate Contractor Agreement (ACA): TBD per individual call/award.

n. Options: TBD per individual call/award.

o. EVMS: TBD on future Calls for each item.

p. Ground and Flight Test: TBD on future Calls for each item.

5. Other Information:

a. Government Furnished Property (GFP) Availability: TBD per individual call.

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 GFP is included in the call or requested in a proposal, the following clauses/provisions apply:

1) FAR 52.245-1 Government Property or FAR 52.245-1, Alt II if the resulting contract is with a nonprofit organization or applied research at nonprofit organizations (Apr 2012);

2) FAR 52.245-9 Use and Charges (Apr 2012);

3) DFARS 252.211-7007, Reporting of Government Furnished Property (Aug

2012);

4) DFARS 252.245-7001, Tagging, Labeling and Marking of Government

Furnished Property (Apr 2012);

5) DFARS 252.245-7002, Reporting Loss of Government Property (Dec 2017);

6) DFARS 252.245-7003, Contractor Property Management System

Administration (Apr 2012);

7) DFARS 252.245-7004, Reporting, Reutilization, and Disposal (Dec 2017).

b. GFI/Software: TBD per individual call/award.

c. Base Support/Network Access: Base Support/Network Access is anticipated and will be determined per individual call.

d. Data Rights: Data Rights will be determined per individual call. Data Rights desired by the contractor should be included with proposal submission as part of the Section K (Reps and Certs). See attachment to ARA.

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 carefully consider 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. Offers that propose delivery of technical data, NCS, or NCS documentation subject to Government Purpose Rights should fully explain how the data was developed at private expense. Specifically, offers 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 technical data, NCS, or NCS documentation subject to Limited Rights, Restricted Rights, or Specifically Negotiated License 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 both the data and each such item, component, or process listed.

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

DFARS 252.227-7014(d) describes requirements for incorporation of third party computer software. Any third party software (commercial and noncommercial) to be incorporated into a deliverable must be clearly identified in the proposal. Prior to delivery of any third party software, the contractor will obtain an appropriate license for the Government, and the written approval of the Contracting Officer.

Any third party software to be delivered to the Government that are not reasonably identifiable at proposal submission, must still be approved by the contracting officer prior to incorporation into a system deliverable. This obligation to obtain pre-approval by the contracting officer, as described above, continues throughout contract administration.

The Government will neither accept nor execute a DD Form 250 for the software deliverables until the Contractor obtains from all third party software suppliers and/or vendors (Licensor) licenses that comply with the following terms and conditions for the Government (Licensee):

1) The license shall not subject the Government to liability that is indefinite or indeterminate, such as an indemnification clause, as it would constitute an obligation in advance or in excess of an appropriation and violate the Anti- Deficiency Act.

2) The license shall not create a contingent liability for the Government. This includes, but is not limited to: unilateral price increases, automatic assessment of charges, and automatic renewal of the license.

3) The license shall be governed by Federal Statutes, Case Law, and Federal Regulations, and shall not be subject to the laws or jurisdiction of any municipality, state, or foreign country.

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

5) The license shall not comment on entitlement to attorney fees.

6) The Licensor shall not have the authority to unilaterally terminate the license. All remedies available shall be consistent with the Disputes Clause in the underlying basic contract.

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

8) The Licensor shall not use any injunctive relief clauses as the Licensor cannot prevent the Licensee from performing mission operations.

9) The Licensor shall not have the authority to control any litigation between a third party and the Licensee.

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

III.Award Information:

1. Anticipated Award Date: TBD per individual call.

2. Anticipated funding: TBD per individual call, to include funding profile.

IV. Eligibility Information:

1. Eligible Offeror: This is an unrestricted solicitation. Businesses/Educational Institutions of all sizes are encouraged to propose on all or any part of this solicitation under each call.

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 Technical POC identified in the Call. 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 anticipated, however, will be considered on a case-by-case basis and identified in each call. If it is determined that foreign participation is not allowed, the US Prime Contractor and/or Sub-Contractor may hire foreign national with prior FDO approval;

however, FNs will be limited to Public Domain information only. Public Domain information is defined as information that is releasable to the general public and sometimes referred to as open source material. Examples include but are not limited to newspapers, magazines and information posted on the internet.

Any proprietary information will have to be appropriately protected.

b. Export Control: This acquisition may involve data that is subject to export control laws and regulations. This determination will be made on a case-by-case basis and identified in each call. If the data is determined to be subject to export control laws, 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, if applicable.

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

NOTE: You may be ineligible for award if all requirements of this solicitation are not met on the white paper/proposal due date as identified in each call.

V. White Paper/Proposal and Submission Information:

1. Overview: White papers and/or proposals submitted under a call shall be in accordance with the instructions provided both in the specific call and this announcement. Each call will identify itself as a one-step or two-step process.

For individual calls, the Government intends to review resulting white papers/proposals and award all, some, or none of the proposal received without negotiations/discussions. However, the Government does reserve the right to negotiate with those offerors whose proposals have been selected for funding.

Offerors should be alert for any ARA/Call amendments that may change proposal requirements or permit extensions to the proposals submission date.

2. White Paper Instructions (Two Step):

a. General Instructions:

1) Offerors will submit a white paper and rough order of magnitude (ROM) cost no later than (NLT) the due date stated within each individual call.

2) White papers must reference the announcement number (FA2377-25-R- B004) and call name/number.

3) Offerors must submit one (1) original and one (1) hard copy of the white paper to the Contracting POC.

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

5) The cost of preparing white papers in response to the ARA 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.

6) NO classified white papers or ROMs will be accepted.

b. Technical:

1) Page Limitations: The following describes the white paper page limitations:

a) White papers shall be limited to (TBD per individual call) pages.

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

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

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

e) All text, including text in tables and charts, must adhere to all font size and line spacing requirements listed herein. Font and line spacing requirements do not have to be followed for illustrations, flowcharts, drawings, and diagrams. These exceptions shall not be used to circumvent formatting requirements and page count limitations by including lengthy narratives in such items.

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

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

i. Section A: Solicitation (FA2377-25-R-B004) and Call Number (TBD per call), 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, the contractor’s Contracting POC and Technical POC with appropriate telephone numbers, fax numbers, and email addresses for the POCs.

ii. Section B: Period of Performance and Task Objectives;

iii. Section C: Technical Summary and Proposed Deliverables; and

iv. Section D: Cost (Rough Order of Magnitude (ROM)).

NOTE: The Government will check the white paper for conformance to the stated requirements. Any pages in excess of the stated page limitation will not be considered for review purposes.

2) The white paper shall include a discussion of the nature and scope of the research and the offeror’s proposed technical approach.

c. Cost: 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.

d. Review: The Government will review the white papers and ROMs in accordance with the White Paper Review Criteria, set forth in Section V below.

Based on this review, the Government will determine which white papers have the potential to best meet Air Force needs. Offerors will be notified of the disposition of their white papers. It is anticipated that Government review of the white papers submitted will take 30 working days.

Those offerors submitting white papers assessed as meeting AF needs will be asked (via RFP) to submit a full technical and cost proposal. Offerors not required to submit proposals will be notified but may, however, still elect to submit. An offeror submitting a proposal without first submitting a white paper will not be eligible for an award.

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

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

3. Proposal Instructions (One Step and/or Request for Proposal):

a. General Instructions:

1) Offerors will submit a technical and cost proposal within TBD working days of the proposal request (to be determined for each call). After receipt, proposals will be reviewed in accordance with the award criteria as defined in the Call. 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

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 FA2377-25-R-B004 and relevant technical area(s) of interest.

5) Offerors must submit one (one) original proposal to the Contracting

POC.

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

7) The cost of preparing proposals in response to this ARA 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.

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

b. Technical/Management Proposal Instructions (One Step or RFP):

1) Page Limitations: The following describes proposal page limitations:

a) The Technical/Management Proposal shall be limited to (TBD per individual call) pages.

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

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

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

e) All text, including text in tables and charts, must adhere to all font size and line spacing requirements listed herein. Font and line spacing requirements do not have to be followed for illustrations, flowcharts, drawings, and diagrams. These exceptions shall not be used to circumvent formatting requirements and page count limitations by including lengthy narratives in such items.

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

g) The proposal page limit does not include the offeror’s proposed Statement of Work (SOW); however, the same formatting rules apply to the SOW, which is limited to (TBD per individual call) pages.

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 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(s) shall include a SOW(s) 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. In addition to the contractor proposed SOW, a Government generated SOW Supplement containing additional contracting requirements will be included in any resulting contracts.

3) Any questions concerning the technical proposal or SOW preparation shall be referred to the Technical POC listed in Overview on page 3 of this solicitation.

c. Cost/Business Proposal Solicited Via Calls (One Step or RFP):

1) Separate the proposal into a business section and cost section. Adequate price competition is anticipated for each call.

a) The Model Contract for FAR-based contracts is provided as the attachment to this document. No sample is provided for Other Transactions. Note that this Model Contract provides examples of clauses that may be included in final contracts, and it provides a basic contract structure. Contracts that are ultimately awarded against the individual calls may vary based on individual program requirements, negotiated terms and conditions, etc. Not all terms and conditions in the Model Contract are applicable to all calls/contracts.

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 Model Contract, any information not technically related, etc. Provide rationale for exceptions to any portion of the Model Contract.

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

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

e) 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. Justification for exceeding the limits must be provided with the proposal.

f) Complete the Representations and Certifications (Section K - attached to this document) and submit with all proposals.

g) If an offeror proposes the use of Government Furnished Property (GFP), other than GFP identified in the call (if applicable), 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) and further summarized for the whole effort. In addition, costs should be broken down and summarized by individual task area. 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 applicable rates, must be broken out with bases clearly identified. The source of labor and overhead rates and all pricing factors should be identified.