TEMPEST ARA FA8650-20-S-1958 - FINAL.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: Trusted and Elastic Military Platforms and Electronic Warfare (EW) System Technologies (TEMPEST)

ARA Type: Initial Announcement

ARA Number: FA8650-20-S-1958

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 11 OCT 2024.

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 Federal Business Opportunities website at http://www.fbo.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.fbo.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): Timothy Matelski AFRL/RYKSW or Richard Bailey, Contracting Officer, AFRL/RYKSW, 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. 2373 or 10 U.S.C 2371(b), 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://farsite.hill.af.mil. 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 $808,505,000.00 with multiple awards ranging from $1,000,000.00 to $200,000,000.00 (the AF http://farsite.hill.af.mil/ 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: AFRL/RYW has a need to investigate and develop methodologies, tools, techniques, and capabilities to identify susceptibilities and mitigate vulnerabilities in avionics systems, protect those systems against cyber-attack, provide simulation capabilities required to develop, mature and transition advanced sensor and avionics technologies, develop platform architecture technologies that enable revolutionary and agile capabilities, and expand emerging open system architecture standards and approaches for existing and next-generation Air Force and DoD weapon systems in multi-domain environments. The goal is to explore new and emerging concepts related to development, integration, assessment, evaluation, and demonstration of cyber security, open system architecture (OSA), novel avionics and sensor technologies, and multi-domain technologies. For this solicitation, avionics is defined to include manned, unmanned, autonomous, and remotely piloted vehicles, on-board Intelligence, Surveillance, and Reconnaissance (ISR) systems, Electronic Warfare (EW) systems, munitions, and any equipment, component, or subsystem that could compromise mission assurance of the Air Force weapon system or tactical platform.

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 Joshua McCamey, Program Manager, AFRL/RYWA

2241 Avionics Circle, WPAFB, OH 45433

(937) 713-8152 or joshua.mccamey@us.af.mil

Secondary Technical POC Jong Hwang, Program Manager, AFRL/RYWA

2241 Avionics Circle, WPAFB, OH 45433

(937) 713-8024 or jong.hwang@us.af.mi

Address contracting questions to the Contracting POCs:

Richard Bailey, Contracting Officer, AFRL/RYKSW 2130 Eighth Street, Bldg. 45, WPAFB, OH 45433

(937) 713-9919 or richard.bailey.26@us.af.mil

Tim Matelski, Contract Negotiator, AFRL/RYKSW 2130 Eighth Street, Bldg. 45, WPAFB, OH 45433

(937) 713-9848 or timothy.matelski@us.af.mil.

Full Text Announcement

I. Program Description: Air Force Research Laboratory, Sensors Directorate (AFRL/RY) 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:

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

The TEMPEST program will investigate, develop, mature, prototype and demonstrate methodologies, tools, techniques, and capabilities to identify susceptibilities and mitigate vulnerabilities in avionics systems, protect those systems against cyber-attack, provide simulation capabilities required to develop, mature and transition advanced avionics and sensor technologies, develop platform architecture technologies that enable revolutionary and agile capabilities, and expand emerging open system architecture (OSA) standards and approaches for existing and next-generation Air Force and Department of Defense (DoD) weapon systems in multi-domain environments.

Calls issued against this ARA will:

• Develop experimental programs that prototype, integrate and demonstrate promising cyber security and cognitive avionics technologies to increase our platforms’ and weapon systems’ survivability and resiliency in the face of multi-domain threats and attacks.

• Develop, experiment, prototype and integrate, in a laboratory environment, new cognitive, cyber hardened and high speed, flexible system architectures.

• Cooperate across the Air Force, DoD, and the Intelligence Community, to develop experimental programs that integrate advanced cyber security and cognitive sensor technologies, techniques, systems and developmental algorithms, new cyber hardened and high speed, flexible system architectures, and advanced avionics, sensors, processing, and exploitation capabilities focused on Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) onto various weapon systems to create revolutionary capabilities.

• Develop experimental programs that implement OSA-based reference architectures to demonstrate the cost and time benefits of applying OSA techniques and align multiple open architecture (OA) standards to prove the interoperability of various standards. Apply and demonstrate tools, technologies, and techniques to more rapidly document, model, simulate, and analyze new OSA-based system capabilities to determine the benefits for individual platforms and the warfighter.

Calls to be issued against the TEMPEST 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 types of work detailed in paragraph I.1.b. below.

a. Technical Areas of Interest:

1) Technologies for Assessing Platform Cyber Security:

Focuses on the design and development of technologies that provide tools to test and experimentation (T&E) units and Cyber units (such as Mission Defense Teams or Red Teams) to assess cyber vulnerabilities in weapon systems with embedded computers.

2) Technologies for Cyber-Hardened Platforms:

Focuses on the design and development of technologies that reduce weapon system vulnerability to cyber-attack.

3) Technologies for Cyber-Resilient Platforms:

Focuses on the design and development of technologies that counter both known and unknown attack vectors that occur during mission operations to maintain mission capability in cyber contested environments.

4) Agile System Architecture Development and Integration:

Focuses on the design/procurement, development and demonstration of tools, technologies, and advanced component prototypes to enable affordable, rapid development and integration of new and emerging warfighting capability. Characteristics of these systems include, but are not limited to: capable of performing multiple functions (e.g., radar, communications, and electronic warfare), capable of fusing different types of data collections (i.e., multiple intelligence (multi-INT)), inherently cyber secure and/or resilient to cyber-attack, and compliant with open system architecture standards and approaches.

5) Open System Architectures for Trusted and Agile Platforms:

Focuses on investigation, through analysis, demonstration and advanced component prototyping, the viability and relevance of current and emerging open system architecture standards and approaches to enable new capability for cyber trusted and agile platforms. This technology area seeks to determine the viability of an OSA implementation prior to system design and development. This technical area shall identify technological advances in open system architecture standards, software, processing, and hardware to demonstrate the viability of modular open system architectures.

6) Technologies for Modeling & Simulation:

Focuses on the discovery, design and implementation of novel technologies to advance the state-of-the-art in modeling/simulation to faithfully represent transmitters, receivers, electronic systems, hostile and friendly radars, and radio frequency propagation algorithms for use with advanced models and simulations.

7) Technologies to Advance RF Simulation:

Focuses on defining simulation requirements for accurately demonstrating and evaluating sensor technologies. This technology area includes the design and implementation of prototype hardware (commercial or custom) and corresponding operating software tools to conduct demonstrations of radio frequency receiving or transmitting systems.

8) Techniques, methods and technologies for measuring sensor system performance:

Focuses on developing simulation techniques and methods to rapidly evolve and evaluate advanced sensors and electronic warfare (EW) technologies demonstrated in laboratory environments. Work under this technical area of interest will develop and employ M&S methods to specify requirements, define architectures, conduct design trades, and report assessment and demonstration results.

b. Development, Experimentation, Test, Evaluation, Assessment, Prototyping, Integration, Ground and Flight Tests/Demonstrations, and Transition Efforts: Various methods will be used to design, develop, prototype, test, evaluate and integrate technologies into systems and systems of systems. Individual calls under this solicitation may include some or all of the following activities and may tailor requirements as appropriate.

1) Technology Development:

The contractor shall develop, prototype, demonstrate and assess technologies and techniques within technical areas of interest defined in paragraph I.1.a. Supporting technologies, tools, techniques and methods required may be provided by the Government or designed by the contractor, and will vary by call. The contractor shall procure the development of software as required per call. Specific topics and requirements will vary by call.

2) Test-Bed Development:

The contractor shall design and develop technologies related to test beds for weapon platforms. Test beds are required to support the design, implementation, and test of technologies, concepts and methodologies foundational to other tasks in this ARA. Specific topics and requirements will vary by call.

3) Test & Integration with Other Programs:

The contractor shall integrate techniques and solutions developed as part of this program as well as other solutions developed under separate contracted programs to produce robust solutions that address the requirements of this solicitation. Techniques and solutions need to address numerous vectors and technology gaps in avionics systems and, as a result, solutions that address different areas of interest will need to be integrated to produce an overall capability demonstration. This task will also apply, integrate, test, and evaluate these solutions relative to specific platforms as directed by AFRL/RYW. Specific topics and requirements will vary by call.

4) Test, Integration & Application of Technologies:

The contractor shall integrate and apply technology as defined in paragraph I.1.a to prototype, Line Replaceable Units (LRUs), subsystems, systems or platforms. Specific requirements will vary by call. The contractor shall also perform system transition activities which may include, but are not limited to:

• Develop transition plans, perform and execute assessments, data collections, and/or modeling and simulation activities for application of technology to production units/systems(s).

• Participate in system deployment, technical troubleshooting, required equipment upgrades, training, and technological input as needed.

• Develop or procure software updates and maintenance for integration into operational systems.

5) Research Networks and Platforms:

The contractor shall develop, operate, and maintain research networks as necessary for tool prototype design, development, and evaluation. The contractor shall ensure the networks adhere to applicable security standards and meet requirements as designed in prototype and as required by AF policy. Specific requirements will vary by call.

6) Integrated Evaluation Methods:

The contractor shall develop real-time simulation methods and technologies to rapidly evolve and evaluate advanced sensors, EW technologies, and enhanced capabilities in an anti-access area denial (A2AD) environment.

This may include development and employment of MS&A methods to define requirements, architectures, hardware and software design trades, costs, and advanced capabilities, and development, definition, and update of technology capability insertion roadmaps and plans based on operational requirements and assessment/demonstration results. Specific requirements will vary by call.

7) Operational Technology Demonstrations and Assessments:

The contractor shall conduct systems engineering, hardware-in-the-loop (HITL) simulation and open-air tests to evaluate and verify operational requirements for weapon systems being used by the USAF, Reserve USAF, and ANG. This may require MS&A as part of a structured system engineering process to develop, integrate, mature, demonstrate, and transition advanced cyber, architecture, open systems and sensor technologies, conduct technology and system evaluations through studies, analyses, hardware and/or software prototyping in laboratory environments to assess technology candidates potential to satisfy operational requirements, to be determined per call. The contractor shall conduct operational threat assessments using techniques such as battlespace simulations, table top exercises or other methods and participate in working groups and analyze threat vectors as required per call.

8) Radio Frequency Synthetic Battlespace Simulation and Generation:

The contractor shall define simulation requirements for RF simulations to accurately demonstrate sensor technology advancements, system capability, and mission improvement. Required activities will vary by call and may include, but are not limited to:

• Conduct threat performance analyses to discover, define, and implement simulation technology into digital models and simulators. The contractor shall participate in threat working groups requiring access to classified intelligence data.

• Define and implement prototype hardware/software necessary to generate RF environments for advanced technology demonstrations.

The contractor shall perform simulations and collect all data required to integrate, mature, and transition EW technologies.

• Develop software tools that support MS&A required for technology demonstrations. Software tools include improved simulation input translation tools (flight path generation, emitter development, and instrumentation scripts), visualization tools for simulation outputs, receiver and jammer evaluation analysis tools that adapt to different vendor output file formats, and improved software modules for RF simulators, to be determined per call.

• Develop closed-loop digital and RF models to demonstrate and assess adaptive, autonomous, or cognitive sensor systems and implement assessment measures to evaluate machine learning systems.

9) Design, develop and evaluate High Fidelity Models:

The contractor shall design, develop, and evaluate high-fidelity models of “red” and “blue” systems/technologies of interest such as, sensors, weapons, command and control algorithms and components, network links, and EW/IO systems and techniques. Required activities will vary by call and may include, but are not limited to:

• Participate in field-testing selected sensor systems to gather data to improve existing and new models.

• Design experiments to evaluate the performance of models, algorithms, and techniques developed under this research technical area.

• Modify, upgrade, integrate, and maintain MS&A frameworks, threat scenarios and software in the loop emulations.

• Use existing and new development models to evaluate, demonstrate and assess the capabilities of sensor and sensor platform technologies and EW/IO techniques.

• Perform laboratory and field experiments, studies, and analyses to support the design, development, and assessment of advanced EW, cyberspace and IO concepts and technologies to improve air survivability. Conduct the experiments, collect and reduce the data, assess the data and report the results.

• Conduct reverse engineering and analysis of threat systems/components and EW/IO concepts/technologies of interest.

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

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

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

5. Other Requirements:

a. Program Security Classification: It is anticipated that the majority of the awards will require Top Secret classification/safeguarding capability, but security classification will be determined for each award. A draft DD254 will not be attached to this ARA, but 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: General Operations Security (OPSEC) procedures, policies and awareness are required in an effort to reduce program vulnerability from successful adversary collection and exploitation of critical information. OPSEC will be applied throughout the life cycle of the contract. The Critical Information List (CIL) and the RY OPSEC Plan will be provided upon request by AFRL/RYOY Information Protection Office. While working on the Government installation, OPSEC guidance and OPSEC training will be provided by AFRL/RYOY Information Protection Office. This training will ensure contractors are familiar with RY’s CIL and RY’s OPSEC Plan as it pertains to their contract.

The contractor shall apply OPSEC in their management of their current program IAW AFI 10-701 Operations Security and WPAFB Supplement to AFI- 10-701.

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

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

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

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

g. 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 http://www.dss.mil/

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.

h. Science and Technology (S&T) Protection: See Attachment: Security Risk Review – AFRLI 61-113. However, the Government may require the offeror to submit additional information &/or a mitigation plan for any identified S&T protection risks. If the Government determines the offeror failed to provide adequate additional information; or an acceptable mitigation plan; or it is determined the offeror’s S&T protection approach is high risk & does not provide adequate protection of S&T information, the Government may reject the proposal & withdraw it from consideration for award.

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

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

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

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

m. Options: TBD per individual call/award.

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

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

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

II. Award Information:

1. Anticipated Award Date: TBD per individual call.

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

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

IV. 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 (FA8650-20-S- 1958) 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 must also include one (1) CD in Microsoft Office or Adobe format containing all electronic versions of the 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.

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

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

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

7) 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 (FA8650-20-S-1958) 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 FA8650-20-S-1958 and relevant technical area(s) of interest.

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

6) Offerors must include one (1) 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) 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.) b) Technical/ Management and Statement of Work must be provided in Microsoft Word, 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 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.

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