FA8650-17-S-6001 - AMENDMENT 7 - 29 Mar 202.pdf

Broad Agency Announcement

Overview Information

THIS SOLICITATION IS NOT REQUESTING ANY WHITE

PAPERS/PROPOSALS AT THIS TIME

NAICS Code: The NAICS Code for this acquisition is 541715 (Research and Technology in the Physical, Engineering, and Life Sciences (except Nanotechnology and Biotechnology) and the small business size standard is 1,000 employees.

Federal Agency Name: Air Force Research Laboratory (AFRL)

Broad Agency Announcement Title: Science and Technology for Autonomous Teammates (STAT)

Broad Agency Announcement Type: This is Amendment 4 to the initial Broad Agency Announcement, FA8650-17-S-6001. This amended BAA solicitation replaces the original solicitation posted 07 July 2017 in its entirety.

Broad Agency Announcement Number: FA8650-17-S-6001

Catalog of Federal Domestic Assistance (CFDA) Number: 12.800 Air Force Defense Research Sciences Program

THIS IS A HYBRID SOLICITATION AGAINST WHICH CALLS AND/OR OPEN

PERIODS WILL BE RELEASED. This BAA will remain open for Calls and potential Open Periods for a period of seventy-two (72) months from the original posting date.

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

Over the period of this BAA, Calls may be issued to request white papers or proposals for specific research 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) or proposals (one-step). 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 Proposal Review Information (section IV.2.). Offerors should monitor https://beta.SAM.gov in the event this announcement is amended or Calls are issued.

For ONE-STEP Calls

First Step: PROPOSAL DUE DATE AND TIME: To be provided in Calls.

For TWO-STEP Calls

First Step: WHITE PAPER DUE DATE AND TIME: To be provided in Calls.

https://beta.sam.gov/

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

B. OPEN Periods (Two-Step, See Section V for instructions):

This BAA may also have Open Periods, which will be announced via Amendments to this overall BAA. White papers may be submitted at any time during an Open Period for specific research area(s) of interest IAW the instructions in Section V. Amendments for Open Periods will specify which Research Area(s) of Interest are open for white papers. White papers will be reviewed and those selected for further consideration will result in a request for proposal (RFP). Proposal due dates and times will be specified in each RFP.

Offerors should monitor the website https://beta.sam.gov/ in the event this announcement is amended.

First Step: WHITE PAPER DUE DATE AND TIME: To be provided in amendments for Open Periods.

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

NOTE: White Paper/proposal receipt after the due date and time shall be governed by the provisions of FAR 52.215-1(c)(3). It should be noted that this installation observes strict security procedures to enter the facility.

These security procedures are NOT considered an interruption of normal Government processes, and proposals received after the above stated date and time as a result of security delays will be considered “late.” Furthermore, note that if offerors utilize commercial carriers in the delivery of proposals, they may not honor time-of-day delivery guarantees on military installations. Be advised, if the U.S. Postal Service is used, building 45 only receives U.S. Postal Mail twice a week and delivery by that means may not meet the proposal due date and time established herein. Early white paper/proposal submission is encouraged.

Submission: White Papers and/or proposals must be submitted to the Contracting Point of Contact (POC): POC will be provided in each Call or Open Period Amendment.

Solicitation Request: White papers or Proposals are not requested at this time.

White papers or proposals will be solicited via Calls (One Step or Two Step) and Amendments for Open Periods (Two Step). Note: Calls and Open Periods for the same research area(s) of interest will not be solicited at the same time.

Technical Read Library: If any additional information (i.e. Government Furnished Information) is required for Calls or Open Periods, the Calls or BAA Amendments for Open Periods will advise offerors of the information and the information will be made available in a Technical Read Library. If information is provided, it is highly recommended that all potential offerors gain access to the technical read library.

A Certified DD Form 2345, Military Critical Technical Data Agreement, shall be submitted with the request to gain access to the technical read library.

System Award Management: To apply for grants and other funding opportunities the applicant entity must be registered in the System for Award Management (SAM). Proposals will not be accepted through Grants.gov or other methods unless the entity is registered in SAM.

Certifications - SAM: SAM is now the central repository for common Government-wide financial assistance certifications and representations.

Registration in SAM now includes the acceptance of Certifications and Assurances.

SAM may be accessed at: https://beta.sam.gov. The Financial Assistance Certifications Report is an attestation that the entity will abide by the requirements of the various laws and regulations; therefore, as applicable, you are still required to submit any documentation, including the SF LLL Disclosure of Lobbying Activities (if applicable), and informing DoD of unpaid delinquent tax liability or a felony conviction under any Federal law.

Type of Contract/Instrument: The Air Force reserves the right to award the instrument best suited to the nature of research proposed. Accordingly, the Government may award any appropriate contract type under the FAR for this research. It is anticipated that awards under this BAA will generally be Cost Plus Fixed Fee (CPFF). Note, cost reimbursement contracts require successful offerors to have an accounting system considered adequate for tracking costs applicable to the contract.

IDIQ (single award, possible multiple award) and “C” type contracts are anticipated under Calls, while “C” type contracts are anticipated under Open Periods. Contract type will be addressed prior to release of Calls or prior to Open Period awards.

Non-traditional offerors are encouraged under this BAA. Other Transactions (OT) for Prototypes and Assistance Instruments (Grants, Cooperative Agreements, TIA, OT for Research) may be awarded under future Calls or Open Periods of the BAA.

Estimated Program Cost: up to $1.9B. Detailed estimated cost or funding profiles will be included in Calls and amendments for Open Periods.

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

Brief Program Summary: The objective of Science and Technology for Autonomous Teammates (STAT) program is to develop and demonstrate autonomy technologies that will enable various AF mission sets. This research will be part of Experimentation Campaigns in: 1 -Multi-domain Command and Control; 2- Intelligence, Surveillance, Recognizance (ISR) Processing Exploitation and Dissemination (PED); and 3- Manned-Unmanned combat Teaming to demonstrate autonomy capabilities to develop and demonstrate autonomy technologies that will improve Air Force operations through human-machine teaming and autonomous decision-making. The technology demonstrations that result from this BAA will substantially improve the Air Force's capability to conduct missions in a variety of environments while minimizing the risks to Airmen. The overall impact of integration of autonomous systems into the mission space will enable the Air Force to operate inside of the enemy’s decision loop.

STAT will develop and apply autonomy technologies to enhance the full mission cycle, including mission planning, mission execution, and post-mission analysis.

Particular areas of interest include multi-domain command and control, manned-unmanned teaming, and information analytics. The technology demonstrations that result from this BAA will substantially improve the Air Force's capability to conduct missions in a variety of environments while minimizing the risks to Airmen. The overall impact of integration of autonomous systems into the mission space will enable the Air Force to operate inside of the enemy’s decision loop.

This effort plans to demonstrate modular, transferable, open system architectures, and deliver autonomy technologies applicable to a spectrum of multi-domain applications. Development efforts will mature a set of technologies that enable airmen to plan, command, control, and execute missions with manageable workloads. The software algorithms and supporting architectures shall:

• Ingest and understand mission taskings and commander’s intent

• Respond appropriately to human direction and orders

• Respond intelligently to dynamic threats and unplanned events

Chosen technologies will be open, reusable, adaptable, platform agnostic, secure, credible, affordable, enduring, and able to be integrated into autonomous systems.

The program will be comprised of various technologies developed by AFRL and Industry, integrated into technology demonstrations and deliverables with all the necessary software, hardware, and documentation to support AFRL-owned modeling and simulation environments for future capability developments. Thus, all technology development efforts must adhere to interface designs and standards.

Communication Between Prospective Offerors and Government Representatives:

Calls: Open communication is encouraged prior to the issuance of a Call. Technical and contracting questions can be resolved in writing or through dialogue until a Call is issued. After a Call is issued, all exchanges shall be in writing and submitted to the Contracting Officer (CO).

If not proprietary or confidential, questions and responses, received under Calls, will be published to beta.SAM (and grants.gov as necessary) to ensure all potential offerors are treated equitably.

Open Periods: Open communication is encouraged prior to submission of proposals (2nd step) under an Open Period. Technical questions can be resolved in writing or through dialogue until proposal submission; however, contracting questions must be in writing. After a proposal is submitted, all exchanges shall be in writing and submitted to the Contracting Officer (CO).

Communications with any of the points of contact shall not constitute a commitment by the Government to subsequently fund or award any proposed effort. Additionally, only Contracting Officers are legally authorized to commit the Government.

Technical POC:

Corey Schumacher, 2698 G. Street, Building 190, Wright-Patterson AFB, OH 45433, 937-356-8834, corey.schumacher@us.af.mil

Contracting POC:

Contracting Officer - Elizabeth A. Fink, 2130 8th Street, Area B, Building 45, Wright- Patterson AFB, OH 45433-7541, 937-713-3361, elizabeth.fink.1@us.af.mil mailto:corey.schumacher@us.af.mil

Full Text Announcement

I. Program Description (Applicable to both Calls and Open Periods): Air Force Research Laboratory (AFRL) will be soliciting for white papers and/or technical and cost proposals through Calls* or Open Periods on the following research effort:

*Reminder, each Call will contain specific requirements, i.e. a Statement of Objectives (SOO) specific to that Call, and pertinent information. A Call may include a SOO with the below listed Research Area(s) of Interest or a SOO which specifies Call objectives which derive from the below Research Area(s) of Interest.

1. Statement of Objectives (SOO)

Program Goals:

The technologies shall enable airman-machine teaming for executing Air Force missions.

The technologies shall enable reduced workload or manning without compromising mission effectiveness or decision timelines.

The technologies shall enable autonomous systems to understand commander’s intent and mission requirements, and adapt to changing circumstances in a manner consistent with commander’s intent.

The technologies shall enable autonomous and unmanned systems to safely and efficiently integrate into Air Force operations.

Program Structure: This effort features EIGHT important research areas of interest, listed below, which include needs for both technology maturation and integration:

1. Mission Planning and Debrief. STAT research must enable platforms to receive information generated during the mission planning process, and provide relevant information during the debrief process, without causing extension of the mission cycle timelines or requiring increased manpower. This area develops the capability for STAT-enabled systems to take in information about the mission plan (including mission contracts, contingencies, targets, frequencies, etc.) that will be necessary to react appropriately and autonomously to events and commands during mission execution. This area is critical for MDC2, ISR PED as well as manned-unmanned teaming.

2. Flight Operations. Autonomous platforms must be able to safely aviate and navigate in ‘military airspace’ with other aircraft, manned and unmanned, while monitoring their own state of health and performing the appropriate actions to ensure safe flight. The platforms must perform basic flight operations to include automated flight modes, flight safety, survivability, and energy resource management. Autonomous vehicle functions enable the execution of mission taskings that span over all mission phases and kill chain elements. These elements are intended to execute the desired vehicle response commanded from other subsystems such as dynamic mission planning. Air and ground collision avoidance capabilities are required, adaptable to varying aircraft capabilities in maneuverability, sensors, and datalinks. Flight Operations is responsible for ensuring continued, safe operation in the presence of flight-critical failures and degradations. It is also responsible for ensuring continued, safe execution of mission tasking in the presence of mission-critical guidance, navigation, and control system failures and degradations.

3. Communications & Datalinks. The communications and data links are responsible for processing, passing and coordinating messages both onboard and between external communication nodes. Technologies are required for dynamic networking capabilities within the full spectrum of communications control and intelligent management of the dissemination of information (the how, when, and how much to communicate in a given environment agnostic of any singular communications medium). This area supports MDC2, ISR PED, and manned-unmanned teaming.

4. Human Interfaces. Human interfaces and decision aids enable the human to team with autonomous systems, leveraging the advantages of both human and machine intelligence. Human interfaces with autonomy platforms must be intuitive and simple for a human to use. This means that direct supervision of all decisions cannot be required. The interfaces provide human awareness and understanding of autonomous system decisions with minimal display clutter, through tailorable human-machine interfaces, effectively alerting the operator when human action is required. This area is critical for MDC2, ISR PED as well as manned-unmanned teaming.

5. Multi-Domain Mission Operations. Multi-Domain Mission Operations is focused on mission execution and operation of mission systems. Major components include:

• Situation understanding through robust sensor exploitation, data analysis, and information sharing

• Dynamic mission planning for contingencies

• Multi-domain command and control

Robust sensor exploitation is essential for the deep understanding of the environment required for autonomous, closed-loop decision-making in a complex mission environment, with applications to autonomous vehicles, command and control, and the processing, exploitation, dissemination (PED) process. The situation understanding capability must provide detection, geolocation, identification and tracking of target and threats using a variety of sensing sources, traditional single and multi-INT fusion, distributed and cooperative techniques, and must operate over a large breadth of operating conditions. Dynamic mission planning determines how to achieve commanded mission effects, and includes task assignment and scheduling across multiple manned and unmanned systems, route planning, and re-planning for any mission contingencies.

Dynamic mission planning and re-planning can occur at vehicle, team, or battlespace levels, and must occur as part of the overall command and control structure. Multi-domain command and control is essential for achieving coordinated effects through the use of heterogeneous assets in air, space, and cyber domains.

6. Executive Functions. The Executive Functions purpose is to provide high-level reasoning capabilities and a goal-prioritization service based on Commander’s Intent. The Executive Function research should support an agent-based model for Observe, Orient, Decide, and Act (OODA-loop).

Information about the operational environment will need a common state representation that allows for rational decision-making based on mission plans and current mission status. Decisions made by the machine will include determining what information must be shared with human operators, when new self-tasking should occur based on opportunity or necessity, planning new possible Courses of Action that achieve Commander’s Intent, and responding to a dynamic battlespace that requires adaptive behavior, such as real-time schedule changes and route planning. This area is critical for MDC2, ISR PED as well as manned-unmanned teaming.

7. System Integration. The technology components and capabilities developed must be capable of being integrated and demonstrated in USAF mission applications. Components should be as platform-agnostic as possible, and be adaptable to different capabilities, sensors, datalinks, etc. with minimal modification. Systems engineering activities are needed to determine functional, physical, and interface architectures, including allocation of tasks between humans and system autonomy.

This activity includes Open System Architecture and Open Technology Development to ensure common interfaces and standards where appropriate. The architectures shall determine how the autonomy functions will be allocated and instantiated, how components will interact, the processing power required, and the information storage/access issues that arise from having distributed autonomous decision-making across multiple platforms and agents.

8. Test and Evaluation, Verification and Validation techniques.

This area is critical for all autonomy research in MDC2, ISR PED and manned-unmanned teaming. The autonomous behaviors developed as part of this effort will require verification and validation, in addition to robust test and evaluation. These test events will stress the response of complex autonomous systems to both planned and unplanned events, and will require cutting edge non-traditional verification and validation techniques. Formal methods specification, simulation-based research & development, and analysis are included in these techniques. Modeling & simulation (M&S) activities will demonstrate technology readiness, air worthiness certification, and/or cyber-security authorization in coordination with existing in-house government M&S activities and support multiple, iterative field or flight test evaluation efforts.

Security: It is expected that during the development and demonstration of technologies supporting the AFRL STAT portfolio that information will be used or generated up to the level of Collateral SECRET. The contractor shall train personnel in, and follow appropriate operations security (OPSEC) measures during the performance of these research activities.

OPSEC: Operations Security (OPSEC) must be an integral part of our daily activities. As we maintain security on our future technologies that are vital to national interest, we must recognize and prepare for the threat poised against our technology. Department of Defense policies mandate a high degree of security throughout the acquisition process. However, heightened security awareness and threat-based countermeasures are particularly essential during the research and development phase when our technology is most vulnerable to espionage, sabotage, or exploitation. It is the obligation of each employee or persons involved on this program to be constantly aware of and strictly adhere to security requirements designed to protect sensitive unclassified and other information and resources produced by acquisition, research and development, and technological security efforts outlined in this BAA. The contractor shall ensure employees receive training and follow appropriate Operations Security (OPSEC) measures during the performance of any resulting awards.

Safety: The contractor shall consider system safety requirements when developing these identified technologies/technical objectives (Ref: Military Standard (Mil-Std 882E Department of Defense Standard Practice System Safety)). The system safety process is to identify and document any system safety hazards introduced during all phases (e.g., planning, design, fabrication and testing) and recommend adequate risk mitigations to either eliminate the identified safety risk or minimize them to acceptable risk level.

The design goal shall be to eliminate all hazards. Any residual hazards and subsequent design risk shall be summarized and provide enough detail to support an informed program management decision with regard to the design’s overall safety risk. The contractor shall conduct an evaluation or assessment of these technologies and recommend appropriate system safety task(s) to be conducted in the appropriate research areas of interest.

Protection of Human Subjects: The Contractor shall comply with the provisions of the following directives/regulations:

- Title 32, Code of Federal Regulations, Part 219 (32 CFR 219), "Protection of Human Subjects"

- Department of Health and Human Services Regulations, "Protection of Human Subjects" (45 CFR Part 46), effective 14 Jul 2009, Subparts A, B, C, & D

- DoD Directive 3216.02, "Protection of Human Subjects and Adherence to Ethical Standards in DoD Supported Research”, (certified current as of 8 Nov 2011)

- Air Force Instruction 40-402, 10 Sep 2014, “Protection of Human Subjects and Adherence to Ethical Standards in Air Force Support Research.”

- AFRL Instruction 40-402, 9 Jul 2014, “Protection of Human Subjects Research”

Interaction with human research subjects shall NOT commence until approval from the Air Force Institutional Review Board (IRB) has been obtained.

Interaction includes communication or interpersonal contact between investigator and subject for the purposes of conducting research.

If an IRB exemption is granted, then the provisions above would no longer be applicable; however, standard ethical principles should still be adhered to.

Investigators should refer to, and abide by, “The Belmont Report: Ethical Principles and Guidelines for Protection of Human Subjects of Research,” 18 April 1979.

Contractor Support to the AFRL Program Design Reviews. The contractor shall support a design review or a series of design reviews during the course of the program. The number of reviews, their timing, and the topics to be covered will be program dependent and shall be determined jointly among the contractor, the AFRL program manager, the program manager’s division technical advisor, and the AFRL Flight test and evaluation (T&E) office. The contractor shall submit the review agenda to the Government for review and approval at least 15 days prior to the desired review date. Review topics shall include at a minimum technical objectives and success criteria, test article description, vehicle modifications, safety systems, airworthiness of vehicle(s) and subsystems, preliminary test plans and schedules, and instrumentation system requirements.

Reference AFRLMAN 99-103, AFRL Flight Test and Evaluation

Contractor Test Plan and Support to the AFRL Safety Review Board (SRB) and Test Review Board (TRB). For all contractual performance that includes a test, experiment, or demonstration on an aerospace vehicle, AFRL must approve the test plan prior to testing, including taxi tests. An aerospace vehicle includes, but is not limited to, a manned vehicle, a remote control (R/C), an uninhabited air vehicle or a remotely powered vehicle. This requirement applies for both government and contractor conducted tests. In accordance with the Contract Data Requirements List (CDRL), the contractor shall submit the draft test plan (using DID DI-NDTI-80566/T for the test plan format) to the government at least 8 weeks prior to testing and the final test plan at least 5 weeks prior to testing for review and approval. The contractor shall support the safety and technical reviews; the contractor shall either attend the reviews or participate via telecom. The decision of the type of contractor support to the reviews will be made by the program manager and technical and safety review board chair.

Reference DID DI-NDTI-80566/T Reference AFRLMAN 99-103, AFRL Flight Test and Evaluation

Contractor Support to AF Mishap Investigations. The contractor shall adhere to AFRLMAN 99-103, AFRL Flight Test and Evaluation, in the event of a mishap (defined as an unplanned event, or a series of events, that result in damage to DoD property, occupational illness to DoD military or civilian personnel, injury to DoD military personnel on- or off-duty, injury to on-duty civilian personnel; damage to public or private property or injury and illness to non-DoD personnel caused by DoD operations). This includes, but is not limited to, immediate access to all test data, test-related documents, and vehicle documentation including, but not limited to, video, pictures, witness statements, onboard recorded data, telemetered data, vehicle systems checks, and vehicle and/or system squawk sheets. If an AFRL representative is not present during the mishap, the contractor shall notify the AFRL program manager of the mishap as soon as practicable after the mishap has been debriefed at the test location but no later than eight (8) hours immediately following the mishap. If the AFRL program manager cannot be reached in person, the contractor shall execute the notification procedures as specified on the AFRL Form 29. In the event of a mishap, the data and information collected must be protected until guidance is provided by a cognizant government representative. It is recommended that the contractor have an established safety representative, through whom communication will occur and the data and information collected will be transmitted to the government.

Reference AFRLMAN 99-103, AFRL Flight Test and Evaluation

Contractor Identified Lessons Learned. The contractor shall provide lessons learned at the completion of the program about the formation, conduct, and reporting of the flight test program to include the design, development, and testing phases to the government using AFRL Form 20, Lessons Learned. However, if the lesson learned is safety related, the contractor shall notify the government program manager immediately.

Reference AFRLMAN 99-103, AFRL Flight Test and Evaluation

2. Within Scope Modifications: Potential offerors are advised that due to the inherent uncertainty of research and development efforts, awards resulting from the Calls or Open Periods under this announcement may be modified during performance to make within scope changes.

3. Deliverable Items:

a. Data Items: Applicable Contract Data Requirements Lists (CDRL) data items will be identified in each Call and Requests for Proposal (2nd Step) under Open Periods. Potential, but not limited to, data items can be found in Attachment 1, the Contract Data Requirements List (CDRL).

b. Software: Software deliverables are anticipated under this program.

Specific software deliverable requirements may be included in Calls or Requests for Proposals (2nd Step) under Open Periods.

c. Hardware: Hardware deliverables are anticipated under this program.

Specific hardware deliverable requirements may be included in Calls or Requests for Proposals (2nd Step) under Open Periods.

d. Prototypes: Prototypes may be required depending on the requirements and will be identified in each Call or Requests for Proposals (2nd Step) under Open Periods.

e. Other: Other deliverables may be required depending on the requirements and will be identified in each Call or Requests for Proposals (2nd Step) under Open Periods.

4. Schedule:

a. Overall effort: Anticipated Period of Performance for awards will be addressed in each Call or Request for Proposal (2nd Step) under Open Periods.

b. Data Items: Data shall be delivered in accordance with the schedule specified in the CDRLs.

c. Software: If applicable, software shall be delivered at completion of technical effort or as specified in each Call or award.

d. Hardware: If applicable, hardware shall be delivered within thirty (30) days after completion of technical effort or as specified in each Call or award

5. Other Requirements:

a. This announcement incorporates FAR and supplement provisions and clauses by reference. The full text of provisions and clauses can be found at http://acquisition.gov

b. Program Security Classification: Security Classification will be determined for each Call/Award. If classified data will be accessed or generated, a facility and storage clearance, at the required classification level, will be required and the proposal will discuss appropriate personnel and facility clearances. Additionally, if a DD254 (Attachment 2) is applicable for a Call/Award, offerors must verify their Cognizant Security Office information is current with Defense Security Service (DSS) at www.dss.mil. Contractors are required to state in the white paper and/or proposal the level of classification to which the contractor is currently approved. All white papers must be unclassified.

c. TEMPEST requirements: N/A

d. OPSEC: See I.1. (Statement of Objectives, Pg. 9 above) for OPSEC guidance.

e. Export Control: Information involved in this research effort is anticipated to 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 proposals.

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

g. Contractor Performance Assessment Reporting System (CPARS) may apply to contract awards resulting from this BAA. If CPARS does apply then 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 (at a minimum). 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.

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

6. Other Information:

a. Government Furnished Property (GFP) Availability: GFP is NOT anticipated. However, GFP will be determined on each Call or Request for Proposal (2nd Step) under Open Periods. 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 solicitation or requested in a proposal the following clauses/provisions apply:

i. FAR 52.245-1 Government Property or FAR52.245-1, Alt I in contracts other than those identified in FAR 45.104(a), or FAR 52.245-1, Alt II if the resulting contract is with a nonprofit organizations or applied research at nonprofit organizations

(APR 2012),

ii. FAR 52.245-9 Use and Charges (APR 2012),

iii. DFARS 252.211.7007, Reporting of Government-Furnished Property

(AUG 2012),

iv. DFARS 252.245-7001, Tagging, Labeling, and Marking of

Government-Furnished Property (APR 2012),

v. DFARS 252.245-7002, Reporting Loss of Government Property

(APR 2012).

vi. DFARS 252.245-7003, Contractor Property Management System

Administration (APR 2012)

vii. DFARS 252.245-7004, Reporting, Reutilization, and Disposal (SEP

2016)

b. Base Support/Network Access: Base support/Network Access is anticipated. Base Support/Network Access will be determined on Calls or Requests for Proposals (2nd Step) under Open Periods.

c. Government Furnished Information (GFI): GFI is anticipated, primarily for modeling and simulation. Government supplied software is possible. If needed, GFI will be identified in a Call or Requests for Proposals (2nd

Step) under Open Periods.

d. Human subjects may be used in the research studies under this effort. If applicable, individual Calls or Request for Proposal (2nd Step) under Open Periods will require Clause 252.235-7004, Protection of Human Subject (Jul 2009), be included in all resulting contracts.

e. Any and all flight tests occurring under this program will be planned, reviewed, approved, and conducted IAW all applicable AF regulations, including but not limited to AFRLMAN 99-103.

f. Data Rights Desired:

(1) Noncommercial Technical Data: Unlimited Rights

(2) Noncommercial Computer Software (NCS): Unlimited Rights

(3) NCS Documentation: Unlimited Rights

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

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

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

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

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

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

Nonconforming data rights assertion lists will not be accepted until submitted in accordance with DFARS 252.227-7017.

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

THIRD PARTY SOFTWARE (COMMERCIAL AND NONCOMMERCIAL):

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

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

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

2. The license shall neither restrict the Government from using the product at various sites nor limit use of the product by various Government agencies or third parties performing work on behalf of the Air Force under the “Science and Technology for Autonomous Teammates (STAT)”. In performance of the “Science and Technology for Autonomous Teammates (STAT)”, Government personnel as well as Government contractors may use the software.

3. The license shall not limit the Government’s use of the software at other Government and Government contractor sites.

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

5. The Licensee shall not be restricted from copying or embedding elements of accessible code into other applications (e.g., nesting code, derivative works).

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

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

“[Section X: deleted; Section Y: amended as follows […]”

If the Licensor will not agree to the terms and conditions cited herein and/or as contained in DFARS 227.72, the Contractor shall retain the current license on behalf of and for the benefit of the US Government if permissible under its license and such use will not subject the Government to the terms of the license.

The Contractor shall provide documentation to clearly correlate or map software license(s) to:

a) Contract Line Item Numbers (CLINS);

b) Contract Deliverables (CDRLS);

c) Paragraphs in the statement of work (SOW); and

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

II. Award Information (Applicable to both Calls and Open Periods)

1. Anticipated Award Date: Anticipated award dates will be included in Calls, Amendment announcing Open Periods, or Requests for Proposals (2nd Step) under Open Periods.

2. Anticipated funding for the overall program is $1.9B. The overall funding profile anticipated for this BAA is as follows:

FY18 $118M

FY19 $152M

FY20 $159M

FY21 $249M

FY22 $326M

FY23 $443M

FY24 $207M

FY25 $246M

Notes:

o The overall BAA active period remains unchanged and ends in FY 23, however FY 24 and FY 25 are captured in this funding profile because awards made prior to BAA expiration in FY 23 could be funded with FY 24 and FY 25 funds.

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

o Each Call, Amendment announcing Open Periods, or Request for Proposals (2nd Step) under Open Periods will have funding profiles specific to that effort. However, similarly, all offerors should be aware that due to unanticipated budget fluctuations, funding in any or all areas may change with little or no notice.

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

III. Eligibility Information (Applicable to both Calls and Open Periods)

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

2. Cost Sharing or Matching: Cost Sharing or Matching will be considered based on the instrument proposed.

3. Federally Funded Research and Development Centers: The following guidance is provided for Federally Funded Research and Development Centers (FFRDCs) contemplating submitting a proposal, as either a prime or subcontractor. FAR 35.017-1(c)(4) prohibits an FFRDC from competing with any non-FFRDC concern in response to a Federal agency request for proposal for other than the operation of an FFRDC (with exceptions stated in DFARS 235.017-1(c)(4)). There is no regulation prohibiting an FFRDC from responding to a solicitation.

However, the FFRDC’s sponsoring agency must first make a determination that the effort being proposed falls within the purpose, mission, general scope of effort, or special competency of the FFRDC, and that determination must be included in the FFRDC’s proposal. In addition, AFRL must make a determination that the work proposed would not place the FFRDC in direct competition with domestic private industry. Only after these determinations are made, would a determination be made concerning the FFRDC’s eligibility to receive an award.

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

5. Other:

a. Foreign Participation: Foreign Nationals (FNs) can be employed by the US Prime Contractor or Sub-Contractor; however, FNs will be limited to Public Domain information unless the contractor has obtained the proper License or Technical Assistance Agreement that authorizes disclosure of Classified Military Information (CMI) and/or Controlled Unclassified Information (CUI) to foreign entities pursuant to the Department of State’s ITAR or Department of Commerce’s EAR.

Additionally, see Attachment 4 (#9) regarding non-US citizens.

b. If an award under this BAA involves data that may be subject to export control laws and regulations, only contractors who are registered and certified with the Defense Logistics Agency and have a legitimate business purpose may participate in the solicitation.

Contact the U.S./Canada Joint Certification Program Office, Defense Logistics Agency, Logistics Information Services J34, HDI Federal Center, 74 Washington Avenue N., Battle Creek, Michigan 49037- 3084, (1-800-352-3572) or the Joint Certification Program Office (JCO) at JCP-Helpdesk@dla.mil for further information on the certification process. You must submit a copy of your approved DD Form 2345, Militarily Critical Technical Data Agreement, with future proposals.

c. Number of Proposals: There are no limits on the number of white papers/proposals an offeror may submit under each Call or Open Period.

d. Eligibility: You may be ineligible for award if all requirements of this solicitation are not met on the due date as identified in each Call or Open Period.

IV. BAA with Calls (one-step/two-step process TBD on each Call) https://www.dla.mil/HQ/LogisticsOperations/Services/JCP/SpecificDD2345Instructions.aspx

Please Note: This is NOT a Call for white papers or proposals. Calls will be released at a later date.

1. Proposal and Submission Information

a. Overview:

This BAA will have Calls that consist of either a one-step or two-step process, described in detail below. For a one-step Call, only proposals will be solicited. For a two-step Call, white papers will be solicited and subsequent request for proposals may follow after peer/scientific reviews. The one-step or two-step process will be determined on each individual Call. A unique Statement of Objectives (SOO) will be included with each Call.

Note: If you intend to submit a proposal for an assistance instrument, go to Attachment 7 which discusses how to find the assistance opportunity, prepare the cover page, and complete the certification. This section also provides the process for electronic submission of proposals for assistance instruments that may be submitted in addition to the proposal instructions specified in each Call.

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

All white paper and proposal submission information for both one- step and two-step Calls will be specified in each Call solicitation.

b. First Step (White Paper) Instructions:

(1) All white paper instructions including General Instructions, page limitations, format, technical portion, cost portion, content summary, and any other information will be specified in each Call.

c. Second Step (Proposal Submission Information) Instructions:

(1) All proposal instructions including General Instructions, page limitations, format, technical/management portion, cost/business portion, cost element breakdown, proposal content summary, funding restrictions, and any other information will be specified in each Call.

2. WHITE…