amend 6 BAA 19-09 second repub (2021).docx

AMENDMENT 6 to BAA FA8750-19-S-7009

The purpose of this modification is to republish the original announcement, incorporating any previous amendments, pursuant to FAR 35.016(c).

This republishing also includes the following changes:

1. Part I, Overview Information:

0. No changes made;

1. Part II, Full Text Announcement:

1. Section IV.2, updates content and format language;

1. Section IV.3.c, updates the mailing instructions;

1. Section IV.4.b. and c, updates clause and provision dates;

1. Section V., adds paragraph 4 regarding adequate price competition;

1. Section VI.1, updates the Proposal Formatting language;

1. Section VI.7, updates the applicable provisions;

1. Section VII: updated the OMBUDSMAN and clause date.

No other changes have been made.

NAICS CODE: 541715

FEDERAL AGENCY NAME: Department of the Air Force, Air Force Materiel Command, AFRL - Rome Research Site, AFRL/Information Directorate, 26 Electronic Parkway, Rome, NY, 13441-4514

BAA ANNOUNCEMENT TYPE: Initial announcement

BROAD AGENCY ANNOUNCEMENT (BAA) TITLE: INFORMATION ANALYSIS FOR MULTI-DOMAIN OPERATIONS AND TARGETING SUPPORT

BAA NUMBER: FA8750-19-S-7009

PART I – OVERVIEW INFORMATION

This announcement is for an Open, 2 Step BAA which is open and effective until 30 Sep 2023. Only white papers will be accepted as initial submissions; formal proposals will be accepted by invitation only. While white papers will be considered if received prior to 3pm Eastern Standard Time (EST) on 30 Sep 2023, the following submission dates are suggested to best align with projected funding:

FY20 by 30 May 2019 FY21 by 30 September 2020 FY22 by 30 September 2021 FY23 by 30 September 2022

Offerors should monitor the Contract Opportunities on the Beta SAM website at https://beta.SAM.gov in the event this announcement is amended.

CONCISE SUMMARY OF TECHNOLOGY REQUIREMENT: The Air Force Research Laboratory - Information Directorate (AFRL/RI) is soliciting white papers under this BAA in the area of multi-domain dynamic target solutions for targeting recommendations through optimization algorithms, sensitivity analysis, and analysis of alternatives. The BAA objective is to conceive, develop and demonstrate innovative and affordable technologies that provide accurate and timely planning and execution against full-spectrum dynamic, time-sensitive or pre-planned targets.

BAA ESTIMATED FUNDING: Total funding for this BAA is approximately $49.9M. Individual awards will not normally exceed 36 months with dollar amounts normally ranging from $500K to $2M. There is also the potential to make awards up to any dollar value as long as the value does not exceed the available BAA ceiling amount of $49.9M.

ANTICIPATED INDIVIDUAL AWARDS: Multiple Awards are anticipated.

TYPE OF INSTRUMENTS THAT MAY BE AWARDED: Procurement contracts, grants, cooperative agreements or other transactions (OT) depending upon the nature of the work proposed. In the event that an Other Transaction for Prototype agreement is awarded as a result of this competitive BAA, and the prototype project is successfully completed, there is the potential for a prototype project to transition to award of a follow-on production contract or transaction. The Other Transaction for Prototype agreement itself will also contain a similar notice of a potential follow-on production contract or agreement.

AGENCY CONTACT INFORMATION: All white paper submissions and any questions of a technical nature shall be directed to the cognizant Technical Point of Contact (TPOC) as specified below (unless otherwise specified in the technical area):

BAA MANAGER:

Michael Manno

AFRL/RIED

525 Brook Rd Rome, NY 13441-4505 Telephone: (315)330-7517 Email: michael.manno@us.af.mil

Questions of a contractual/business nature shall be directed to the cognizant contracting officer, as specified below (email requests are preferred):

Amber Buckley Telephone (315) 330-3605 Email: amber.buckley@us.af.mil

Emails must reference the solicitation (BAA) number and title of the acquisition.

Pre-Proposal Communication between Prospective Offerors and Government Representatives: Dialogue between prospective offerors and Government representatives is encouraged. Technical and contracting questions can be resolved in writing or through open discussions. Discussions with any of the points of contact shall not constitute a commitment by the Government to subsequently fund or award any proposed effort. Only Contracting Officers are legally authorized to commit the Government.

Offerors are cautioned that evaluation ratings may be lowered and/or proposal rejected if proposal preparation (Proposal format, content, etc.) and/or submittal instructions are not followed.

PART II – FULL TEXT ANNOUNCEMENT

BROAD AGENCY ANNOUNCEMENT (BAA) TITLE: MULTI-DOMAIN OPERATIONS AND INFORMATION ANALYSIS

BAA NUMBER: BAA FA8750-19-S-7009

CATALOG OF FEDERAL DOMESTIC ASSISTANCE (CFDA) Number: 12.800

I. TECHNOLOGY REQUIREMENTS:

The Air Force Research Laboratory - Information Directorate (AFRL/RI) is soliciting white papers under this BAA in the area of multi-domain operations, information, and dynamic targeting solutions for targeting recommendations through optimization algorithms, sensitivity analysis, and analysis of alternatives. The BAA objective is to conceive, develop and demonstrate innovative and affordable technologies that provide accurate and timely planning and execution against full-spectrum dynamic, time-sensitive or pre-planned targets. The intent is to provide research, development, integration, test and evaluation of technologies/techniques for the Air Operations Center (AOC) and Combatant Command targeting needs. With dynamic targeting occurring in a compressed timeline on targets outside of the Air Tasking Order (ATO), this fast-paced activity allows for little time to conduct analysis on the target or assign the optimal asset to use for targeting. Conduct research to develop and demonstrate innovative and affordable technologies that provide a more lethal, disruptive, and resilient Air Force (AF) targeting production capability through the application of algorithmic warfare, artificial intelligence, and automation.

1. Technical Areas This announcement is divided into four (4) technical areas (TAs) and three (3) knowledge areas (KAs). The knowledge areas were added to this announcement to provide context on the technical areas needed for research and development. Proposers may submit offers on any technical area individually or any combination of technical areas thereof. It is also recommended that proposers take KAs into consideration. Proposers who include multiple technical areas in their proposal should describe the work for each technical area separately and clearly identify the applicable TAs. This is an applied research type program. Proposers should indicate their integration strategy to integrate components developed in other TAs when applicable. The initial effort for each TA should be focused on establishing the basic functionality of key components for Multi-Domain Dynamic Targeting. Only after these components are realized should additional capabilities be added. Additionally, there are some areas the proposers should be knowledgeable of or willing to rapidly learn since not much time will be allotted to become experts in targeting.

Technical Area 1. Optimization The goal of Multi-objective Optimization is to analyze the targeting process, identify processes which can be improved via optimization, and develop a multi-objective framework for performing optimization across these processes. These processes will include, but are not limited to, identifying available resources, performing weaponeering, selecting ideal available weapon effects, and selecting most appropriate platform for effect delivery. The result of the optimization is to be a ranked list of suggested courses of action. Optimization will be performed with the goal of reducing mission planning time, decreasing overall mission cost, and increasing mission success rates, with reduced human overhead. These objectives are to be weighted to reflect commander’s intent, though other objectives may also be used to supplement. Targeting sub-processes may be modeled as analogues to classical Mixed-Integer Linear Programing (MILP) problems, or through the creation of custom objective functions and tailored solvers. In either case, clear mathematical representations for each objective must be provided, with detailed reasoning behind formulation decisions. This will support future alterations and additions as targeting evolves.

The optimization framework must be capable of ingesting the diverse data formats that are critical to the targeting process. It should also estimate the time required to solve each objective function for each problem, as this will identify bottlenecks and determine infeasible solutions as the window of opportunity decreases. While the initial effort should focus on applying kinetic effects, the framework must be constructed with the intent of domain-agnosticism, to support future development into non-kinetic effects.

Technical Area 2. Modeling and Simulation.

The purpose of Technical Area 2 is to create models that simulate Multi-Domain Command and Control (MDC2) operations, and utilizing dynamic targeting scenarios. These scenarios should have the ability to add or inject MDC2 technologies to determine how new technologies can shape the battlespace. The model design may create scenarios that create quandaries to force application due to insufficient battle space awareness due to the “fog-of-war”. Comprehensive battlespace awareness provides the basis for planning and execution efforts. It provides predictive and actionable intelligence, ISR operations, and targeting in a manner that supports air tasking, execution, and assessment. From a multi-domain perspective, the development of comprehensive battlespace awareness is challenged by the need to integrate information from multiple sources of varying quality across command chains, over multiple networks and classification levels to understand the nature of developing events and their consequences from a geographic or global perspective.

The MDC2 objective for battlespace awareness activities, ostensibly, is to develop and maintain a shared understanding of the operational environment that spans geographic, functional, domain, classification, and organizational boundaries. The scope of such awareness includes information on friendly forces, ongoing operations, adversary forces, indications and warnings, possible targets, as well as military, political, environmental, and other events. It entails understanding not only what events are taking place throughout the battlespace irrespective of domain, but also establishing how they may impact each other, cross geographic areas of responsibility, affect campaign plans, and hamper (or even enhance) the commander’s ability to project force and create effects.

Modeling and Simulation may be mathematical, physical or computer based and may include, but are not limited to:

1. Real-time visualization and playback (i.e. VESPA)

2. User-interrupted simulation design (i.e. WARLOCK)

3. Discrete or continuous event simulations

4. Linear or non-linear programming

5. Wargaming

Technical Area 3. Workflow Analysis The purpose of Workflow Analysis is to elicit established dynamic targeting workflows. The idea is to use workflow methodologies to understand work processes and output, grounded in a social and technical framework. It should take into account the overall functionality and purpose of the entire organization (with boundary conditions set as appropriate) as well as the specific goals of the teams associated with key processes of interest. Minimally consider the work domain, tasks, strategies as well as the social/cultural aspects of the organization as well as the required skillsets of those involved in the work processes.

In general:

· Describe stakeholder tasks and roles

· Assess stakeholder familiarity with the work products

· Describe current uses of the work products within their workflow

· Describe envisioned uses of the work products within their workflow

· Document sources (organizations and products) that provide information similar to that of the work product

· Communicate requirements/process in interacting with the targeting team requesting the work product and/or providing feedback regarding the work product

· Elicit specific recommendations regarding work product production process, content, and/or format that would allow end users to better utilize the work product within their workflow Specifically, describe the primary components:

1. Sequence of repetitive tasks

0. Linear, discrete stages

0. Standardized procedures and performance criteria

1. Human performance

1. Individual-level cognitive and manual skills

1. Team-level communication and coordination

1. IT Tools

2. Knowledge management

2. Systems management

1. Work flow

3. Use any appropriate Business Process Management (BPM) computer tool model to create business workflows.

Technical Area 4. Virtual and Augmented Reality Virtual Reality (VR) is a technology that takes place within a simulated environment which uses computational data to immerse the user within a realistic construct. This gives the illusion of your presence in an environment similar to the real world. VR technology is used across all branches of the military, within the Intelligence Community and within the Department of Homeland Security for flight and battlefield simulation.

Augmented Reality (AR) takes VR and overlays other information from various sources and creates a multi-dimensional “info-sphere” where the user can better determine the effects of various factors upon their current/future position. This fused view can enhance mission effectiveness and enable better decisions.

The purpose of Virtual and Augmented reality is to create a representation of a Region of Interest (ROI) with information pulled from multiple sources, in real-time, or near real-time, to build an immersive environment of a single location, which enables ease of interaction, for an analyst or a team of analysts, in different locations.

Additionally, create a user friendly info-sphere with the capability to display a multitude of information to foster potential multi-domain data fusion. This capability includes the real-time/near real-time ability to dynamically regenerate a new ROI or incorporate changes in an existing ROI. The system will also be capable of point mensuration; a process that will allow for measurement of a feature or location on the earth to determine an absolute latitude, longitude, and elevation. It should also allow for the introduction of photogrammetry which models geometric information about a target to support precise evaluation of physical effects.

The vision is to make the VR Info-sphere's COP viable, and as new data is captured and technologies advance, they will become auto-integrated into dynamic display for targeteers. This 3D model of the ROI would be exportable/shareable between future ground forces Augmented Reality (AR) headsets/display units (e.g. mission adaptive ballistic goggles/helmets, etc).

Knowledge Area 1. Multi-Domain Operations (MDO).

Advanced Integrated Air Defense Systems, Anti-satellite, and computer network attack weapons can hold capabilities in air, space and cyber at risk and create Anti-Access and Area Denial (A2AD) quandaries. The goal of Multi-Domain Operations is to ensure the ability to integrate operations in multiple domains and create complex dilemmas for potential adversaries; success is dependent on the ability to harness information and conduct advanced command and control in all domains, simultaneously. Including advanced command and control (C2) capabilities to meet evolving threats, as the Air Force continues to leverage air, space and cyberspace operations, progressing from enhanced operational effects to truly synergistic effects.

The need for Multi-Domain Command and Control (MDC2) stems from the notion that conflict in the Digital Age will be characterized as multi-domain, multi-region, multi-component, and multi-nation. These characteristics will create operational seams for our forces that must be overcome in an operationally agile way. MDC2 represents the Air Force’s concept for how to mitigate the negative effects of these seams with operational agility and high velocity decision making.

Research and development areas addressing MDO may include, but are not limited to:

1. Perpetually enhance warfighting C2 concepts for all domain capabilities to improve integration and interdependence;

2. Perpetually enhance multi-domain capabilities;

3. Perpetually enhance C2 processes to optimize MDO;

4. Leverage agile acquisition to field C2 systems in support of MDO;

5. Deliver assured communications networks to enable C2 in contested environments;

6. Leverage advanced technology (Artificial Intelligence, Machine Learning, etc.) to enhance and accelerate C2 functions;

7. Continually improve C2 interoperability with joint, coalition and interagency forces.

Knowledge Area 2. Dynamic Targeting Dynamic targeting prosecutes targets of opportunity that are identified too late, or not selected for action in time to be included in deliberate targeting but, when detected or located, meet criteria specific to achieving objectives. When plans change and planned targets must be adjusted, dynamic targeting can also manage those changes.

1. Dynamic targeting is exclusive to phase 5 of the Joint Targeting Cycle. Phase 5 itself consists of five steps:

1. Find. During this step, possible targets are detected and classified for further prosecution.

1. Fix. The fix step of dynamic targeting includes actions to determine the location (fix) of the potential target.

1. Track. During this step, the target is observed and its activity and movement are monitored.

1. Target. During this step the decision is made to engage the target in some manner to create desired effects and the means to do so are selected and coordinated.

1. Engage. In this step, action is taken against the target.

The steps of dynamic targeting may be accomplished iteratively and in parallel. The find, fix, and track steps tend to be ISR-intensive, while the target and engage steps are typically labor-force,and decision-making intensive.

During execution, as armed conflict is a dynamic event, some targets will be identified as emerging targets or not selected for execution in time to be included in the normal targeting process. These targets must be prosecuted on a compressed timeline than those that are prosecuted using deliberate targeting. Consequently, automating and expediting the flow of information, from nomination, through development and execution, and then back to the targeteers, becomes even more critical in these instances.

Knowledge Area 3. Weaponeering.

Weaponeering may be defined as the process of determining the quantity of a particular type of weapon required to achieve a specific level of target damage by considering the effects of target vulnerability, warhead damage mechanism, delivery errors, damage criterion and weapon reliability. Effective use of Weaponeering methodologies will produce the most efficient way to inflict the prescribed amount of damage to the intended target thereby reducing exposure of war fighters to enemy threats and minimizing collateral damage to non-combatant personnel and infrastructure (www.weaponeering.com).

The objective in weaponeering knowledge, is to understand the difficulties Air Force Targeteers encounter when dealing with little to no data, and still needing to compute a probability of effect for a given target. There is a plethora of information regarding target vulnerability and damage mechanisms in the kinetic effects domain mostly hosted in the Joint Munitions Effectiveness Manual, JMEM Weaponeering System (JWS). The idea is to significantly reduce the dynamic targeting process by automating weaponeering solutions. Possible Machine Learning applications could be used to “teach” a machine to quickly determine a weaponeering solution and provide rapid options to targeteers dealing in the real time realm. In this realm there is not time to fully compute a weaponeering solution. That is left for the deliberate targeting process. The objective is to develop such capability to ingest into an optimization algorithm that will present decision makers with options.

The Questions and Answers (Q&A) from the 29 MAR Industry Day are attached to this announcement.

IMPORTANT NOTE: The Industry Day slides are considered Distribution Statement C and are available to U.S. Government agencies and their Contractors. Therefore, access will require additional approval.

Contact the Technical Point of Contact identified in Section VII, to receive this material. When doing so, the requestor must:

Provide their company’s CAGE Code;

Be a U.S. owned company (if not, see Section III for mitigation procedures); and Be. a U.S. citizen The materials will then be provided via digital transmission of materials by secured means.

IMPORTANT NOTES REGARDING:

FUNDAMENTAL RESEARCH. It is DoD policy that the publication of products of fundamental research will remain unrestricted to the maximum extent possible. National Security Decision Directive (NSDD) 189 defines fundamental research as follows:

‘Fundamental research’ means basic and applied research in science and engineering, the results of which ordinarily are published and shared broadly within the scientific community, as distinguished from proprietary research and from industrial development, design, production, and product utilization, the results of which ordinarily are restricted for proprietary or national security reasons.

As of the date of publication of this BAA, the Government cannot identify whether work proposed under this BAA may be considered fundamental research and may award both fundamental and non-fundamental research. Proposers should indicate in their proposal whether they believe the scope of the research included in their proposal is fundamental or not. While proposers should clearly explain the intended results of their research, the Government shall have sole discretion to select award instrument type and to negotiate all instrument terms and conditions with selectees. Appropriate clauses will be included in resultant awards for non-fundamental research to prescribe publication requirements and other restrictions, as appropriate.

For certain research projects, it may be possible that although the research being performed by the awardee is restricted research, a sub-awardee may be conducting fundamental research. In those cases, it is the awardee’s responsibility to explain in their proposal why its sub-awardee’s effort is fundamental research.

CLOUD COMPUTING. In accordance with DFARS Clause 252.239-7010, if the development proposed requires storage of Government, or Government-related data on the cloud, offerors need to ensure that the cloud service provider proposed has been granted Provisional Authorization by the Defense Information Systems Agency (DISA) at the level appropriate to the requirement.

II. AWARD INFORMATION:

1. FUNDING: Total funding for this BAA is approximately $49.9M. The anticipated funding to be obligated under this BAA is broken out by fiscal year as follows:

FY19 - $10.75M

FY20 - $14.55M

FY21 - $14.23M

FY22 - $7.98M

FY23 – $2.40M

1. Individual awards will not normally exceed 36 months with dollar values normally ranging from $500k to $2M. There is also the potential to make awards up to any dollar value as long as the value does not exceed the available BAA ceiling amount.

1. The Government reserves the right to select all, part, or none of the proposals received, subject to the availability of funds. All potential Offerors should be aware that due to unanticipated budget fluctuations, funding in any or all areas may change with little or no notice.

2. FORM. Awards of efforts as a result of this announcement will be in the form of contracts, grants, cooperative agreements or other transactions depending upon the nature of the work proposed.

3. BAA TYPE: This is a two-step open broad agency announcement. This announcement constitutes the only solicitation.

As STEP ONE – The Government is only soliciting white papers at this time. DO NOT SUBMIT A FORMAL PROPOSAL. Those white papers found to be consistent with the intent of this BAA may be invited to submit a technical and cost proposal. See Section VI of this announcement for further details regarding the proposal.

III. ELIGIBILITY INFORMATION:

1. ELIGIBILITY: All qualified offerors who meet the requirements of this BAA may apply.

2. FOREIGN PARTICIPATION/ACCESS:

1. This BAA is closed to foreign participation. This includes both foreign ownership and foreign nationals as employees or subcontractors.

1. Exceptions.

1. Fundamental Research. If the work to be performed is unclassified, fundamental research, this must be clearly identified in the white paper and/or proposal. See Part II, Section I for more details regarding Fundamental Research. Offerors should still identify any performance by foreign nationals at any level (prime contractor or subcontractor) in their proposals. Please specify the nationals’ country of origin, the type of visa or work permit under which they are performing and an explanation of their anticipated level of involvement. You may be asked to provide additional information during negotiations in order to verify the foreign citizen’s eligibility to participate on any contract or assistance agreement issued as a result of this announcement

1. Foreign Ownership, Control or Influence (FOCI) companies who have mitigation plans/paperwork in place. Proof of approved mitigation documentation must be provided to the contracting office focal point, Amber Buckley, Contracting Officer, telephone (315) 330-3605, or e-mail Amber.Buckley@us.af.mil prior to submitting a white paper and/or a proposal. For information on FOCI mitigation, contact the contact the Defense Counterintelligence and Security Agency (DCSA). Additional details can be found at: https://www.dcsa.mil/mc/ctp/foci/

1. Foreign Nationals as Employees or Subcontractors. Applicable to any effort not considered Fundamental Research. Offerors are responsible for ensuring that all employees and/or subcontractors who will work on a resulting contract are eligible to do so. Any employee who is not a U.S. citizen or a permanent resident will be restricted from working on any resultant contract unless prior approval of the Department of State or the Department of Commerce is obtained via a technical assistance agreement or an export license. Violations of these regulations can result in criminal or civil penalties.

1. Information Regarding Non-US Citizens Assigned to this Project

0. Contractor employees requiring access to USAF bases, AFRL facilities, and/or access to U.S. Government Information Technology (IT) networks in connection with the work on contracts, assistance instruments or other transactions awarded under this BAA must be U.S. citizens. For the purpose of base and network access, possession of a permanent resident card ("Green Card") does not equate to U.S. citizenship. This requirement does not apply to foreign nationals approved by the U.S. Department of Defense or U.S. State Department under international personnel exchange agreements with foreign governments. It also does not apply to dual citizens who possess US citizenship, to include Naturalized citizens. Any waivers to this requirement must be granted in writing by the Contracting Officer prior to providing access. Specific format for waiver request will be provided upon request to the Contracting Officer. The above requirements are in addition to any other contract requirements related to obtaining a Common Access Card (CAC).

0. For the purposes of Paragraph 1, it an IT network/system does not require AFRL to endorse a contractor's application to said network/system in order to gain access, the organization operating the IT network/system is responsible for controlling access to its system. If an IT network/system requires a U.S. Government sponsor to endorse the application in order for access to the IT network/system, AFRL will only endorse the following types of applications, consistent with the requirements above:

1. Contractor employees who are U.S. citizens performing work under contracts, assistance instruments or other transactions awarded under this BAA.

1. Contractor employees who are non-U.S. citizens and who have been granted a waiver.

Any additional access restrictions established by the IT network/system owner apply.

3. FEDERALLY FUNDED RESEARCH AND DEVELOPMENT CENTERS AND GOVERNMENT ENTITIES: Federally Funded Research and Development Centers (FFRDCs) and Government entities (e.g., Government/National laboratories, military educational institutions, etc.) are subject to applicable direct competition limitations and cannot propose to this BAA in any capacity unless they meet the following conditions:

1. FFRDCs: FFRDCs must clearly demonstrate that the proposed work is not otherwise available from the private sector; and FFRDCs must provide a letter on official letterhead from their sponsoring organization citing the specific authority establishing their eligibility to propose to Government solicitations and compete with industry, and their compliance with the associated FFRDC sponsor agreement’s terms and conditions. This information is required for FFRDCs proposing to be prime contractors or sub-awardees.

1. Government Entities: Government entities must clearly demonstrate that the work is not otherwise available from the private sector and provide written documentation citing the specific statutory authority and contractual authority, if relevant, establishing their ability to propose to Government solicitations. While 10 U.S.C.§ 2539b may be the appropriate statutory starting point for some entities, specific supporting regulatory guidance, together with evidence of agency approval, will still be required to fully establish eligibility.

FFRDC and Government entity eligibility will be determined on a case-by-case basis; however, the burden to prove eligibility for all team members rests solely with the proposer.

Government agencies interested in performing work related to this announcement should contact the Technical Point of Contact (TPOC). If resulting discussions reveal a mutual interest, cooperation may be pursued via other vehicles.

IV. APPLICATION AND SUBMISSION INFORMATION:

All responses to this announcement must be addressed to the Technical Point of Contact (TPOC) listed in SECTION VII. DO NOT send white papers to the Contracting Officer.

1. SUBMISSION DATES AND TIMES:

It is recommended that white papers be received by 3 PM Eastern Standard Time (EST) on the following dates to maximize the possibility of award:

FY20 by 30 May 2019 FY21 by 30 September 2020 FY22 by 30 September 2021 FY23 by 30 September 2022

White papers will be accepted until 3 PM EST, but it is less likely that funding will be available in each respective fiscal year after the dates cited. This BAA will close on 30 SEP 2023.

All offerors submitting white papers will receive notification of their evaluation results within 45 days of submission. Offerors should email the TPOC and the Contracting Officer listed in Section VII, for status of their white paper(s) after 45 days, if no such correspondence has been received.

2. CONTENT AND FORMAT: Offerors are required to submit 2 copies of a 3 to 5 page white paper summarizing their proposed approach/solution. The purpose of the white paper is to preclude unwarranted effort on the part of an offeror whose proposed work is not of interest to the Government.

The white paper will be formatted as follows:

1. Section A: Title, Period of Performance, Estimated Cost, Name/Address of Company, Technical and Contracting Points of Contact (phone and email)(this section is NOT included in the page count);

1. Section B: Task Objective; and

1. Section C: Technical Summary and Proposed Deliverables.

All white papers shall be double spaced with a font no smaller than 12 point. Please note that less than 12 point font is acceptable for graphics and illustrations (as in labels and short descriptions) as long as it is readable when printed out on standard 8x11 paper. In addition, respondents are requested to provide their Commercial and Government Entity (CAGE) Code, their unique entity identifier and electronic funds transfer (EFT) indicator (if applicable), an e-mail address and reference BAA FA8750-19-S-7009 with their submission.

Multiple white papers within the purview of this announcement may be submitted by each offeror. If the offeror wishes to restrict its white papers, they must be marked with the restrictive language stated in FAR 15.609(a) and (b).

3. HANDLING AND MAILING INSTRUCTIONS:

a. CLASSIFICATION GUIDANCE. All Proposers should review the NATIONAL INDUSTRIAL SECURITY PROGRAM OPERATING MANUAL, (NISPOM), dated February 28, 2006 and incorporating Change 2, dated May 18, 2016, as it provides baseline standards for the protection of classified information and prescribes the requirements concerning Contractor Developed Information under paragraph 4-105. Defense Counterintelligence and Security Agency (DCSA) Site for the NISPOM is: http://www.dcsa.mil/.

In the event of a possible or actual compromise of classified information in the submission of your white paper or proposal, immediately but no later than 24 hours, bring this to the attention of your cognizant security authority and AFRL Rome Research Site Information Protection Office (IPO):

Information Protection Office (contact only if a security compromise has occurred)

b. CLASSIFIED SUBMISSIONS. AFRL/RIED will accept classified responses to this BAA when the classification is mandated by classification guidance provided by an Original Classification Authority of the U.S. Government, or when the offeror believes the work, if successful, would merit classification.

Security classification guidance in the form of a DD Form 254 (DoD Contract Security Classification Specification) will not be provided at this time since AFRL is soliciting ideas only.

Offerors that intend to include classified information or data in their white paper submission or who are unsure about the appropriate classification of their white papers should contact the technical point of contact listed in Section VII for guidance and direction in advance of preparation.

c. MAILING INSTRUCTIONS.

Email Unclassified electronic submission to the TPOC identified in Section VII. Encrypt or password-protect all proprietary information prior to sending. Offerors are responsible to confirm receipt with the TPOC. AFRL is not responsible for undelivered documents. If electronic submission is used, only one copy of the documentation is required.

Questions can be directed to the TPOC listed in Section VII.

4. OTHER SUBMISSION REQUIREMENTS/CONSIDERATIONS:

a. COST SHARING OR MATCHING: Cost sharing is not a requirement. Cost sharing may be proposed and will be considered on a case-by-case basis.

b. SYSTEM FOR AWARD MANAGEMENT (SAM). Offerors must be registered in the SAM database to receive a contract award, and remain registered during performance and through final payment of any contract or agreement. Processing time for registration in SAM, which normally takes forty-eight hours, should be taken into consideration when registering. Offerors who are not already registered should consider applying for registration before submitting a proposal. The provision at FAR 52.204-7, System for Award Management (Oct 2018) applies.

c. EXECUTIVE COMPENSATION AND FIRST-TIER SUBCONTRACT/ SUBRECIPIENT AWARDS: Any contract award resulting from this announcement may contain the clause at FAR 52.204-10 - Reporting Executive Compensation and First-Tier Subcontract Awards (Jun 2020). Any grant or agreement award resulting from this announcement may contain the award term set forth in 2 CFR, Appendix A to Part 25 which can be viewed at: http://www.ecfr.gov/cgi-bin/text-idx?SID=8fb6c83606df57968c3e7e145e7d683c&mc=true&node=ap2.1.25_1360.a&rgn=div9

d. ALLOWABLE CHARGES: The cost of preparing white papers/proposals in response to this announcement is not considered an allowable direct charge to any resulting contract or any other contract, but may be an allowable expense to the normal bid and proposal indirect cost specified in FAR 31.205-18. Incurring pre-award costs for ASSISTANCE INSTRUMENTS ONLY are regulated by 2 CFR part 200.458, Pre-Award Costs.

e. GOVERNMENT APPROVED ACCOUNTING SYSTEM: An offeror must have a government approved accounting system prior to award of a cost-reimbursement contract per limitations set forth in FAR 16.301-3(a) to ensure the system is adequate for determining costs applicable to the contract. The acceptability of an accounting system is determined based upon an audit performed by the Defense Contract Audit Agency (DCAA). IMPORTANT: If you do not have a DCAA approved accounting system access the following link for instructions: https://beta.sam.gov/opp/e628c811fafe041accdddf55fb8539bf/view?keywords=AFRL-BAA-Guide&sort=-relevance&index=&is_active=true&page=1

f. HUMAN USE: All research involving human subjects, to include the use of human biological specimens and human data, selected for funding must comply with Federal regulations for human subject protection. Further, research involving human subjects that is conducted or supported by the DoD must comply with 32 CFR 219, “Protection of Human Subjects” found at: http://www.access.gpo.gov/nara/cfr/waisidx_07/32cfr219_07.html, and DoD Instruction 3216.02, “Protection of Human Subjects and Adherence to Ethical Standards in DoD-Supported Research” found at: http://www.dtic.mil/whs/directives/corres/pdf/321602p.pdf.

1. Institutions awarded funding for research involving human subjects must provide documentation of a current Assurance of Compliance with Federal regulations for human subject protection, for example a Department of Health and Human Services, Office of Human Research Protection Federal Wide Assurance found at: http://www.hhs.gov/ohrp.

1. All institutions engaged in human subject research, to include subcontractors, must have a valid assurance. In addition, personnel involved in human subject research must document the completion of appropriate training for the protection of human subjects.

1. For all research that will involve human subjects in the first year or phase of the project, the institution must submit evidence of a plan for review by an institutional review board (IRB) as part of the proposal. The IRB conducting the review must be the IRB identified on the institution’s Assurance of Compliance. The protocol, separate from the proposal, must include a detailed description of the research plan, study population, risks and benefits of study participation, recruitment and consent process, data collection, and data analysis. The designated IRB should be consulted for guidance on writing the protocol. The informed consent document must comply with 32 CFR 219.116. A valid Assurance of Compliance and evidence of appropriate training by all investigators should accompany the protocol for review by the IRB.

1. In addition to a local IRB approval, an AFRL-level human subject regulatory review and approval is required for all research conducted or supported by the DoD. The Air Force office responsible for managing the award can provide guidance and information about the AFRL-level review process. Confirmation of a current Assurance of Compliance and appropriate human subjects protection training is required before AFRL-level approval can be issued.

1. The time required to complete the IRB review/approval process will vary depending on the complexity of the research and/or the level of risk to study participants; ample time should be allotted to complete the approval process. The IRB approval process can last between 1 to 3 months, followed by a DoD review that could last 3 to 6 months. No funding may be used toward human subject research until all approvals are granted. Therefore, in their cost proposals offerors should separate human use into a separate option.

V. APPLICATION REVIEW INFORMATION:

1. CRITERIA: The following criteria, which are listed in descending order of importance and will be used to determine whether white papers and proposals submitted are consistent with the intent of this BAA and of interest to the Government:

No further evaluation criteria will be used to select white papers for proposal invitation. Proposals will be evaluated IAW this evaluation criteria only and categorized/selected for award as detailed in Section V.2.b.2. White papers and proposals submitted will be evaluated as they are received.

2. REVIEW AND SELECTION PROCESS:

1. Only Government employees will evaluate the white papers/proposals for selection. The Air Force Research Laboratory's Information Directorate has contracted for various business and staff support services, some of which require contractors to obtain administrative access to proprietary information submitted by other contractors. Administrative access is defined as "handling or having physical control over information for the sole purpose of accomplishing the administrative functions specified in the administrative support contract, which do not require the review, reading, and comprehension of the content of the information on the part of non-technical professionals assigned to accomplish the specified administrative tasks." These contractors have signed general non-disclosure agreements and organizational conflict of interest statements. The required administrative access will be granted to non-technical professionals. Examples of the administrative tasks performed include: a. Assembling and organizing information for R&D case files; b. Accessing library files for use by government personnel; and c. Handling and administration of proposals, contracts, contract funding and queries. Any objection to administrative access must be in writing to the Contracting Officer and shall include a detailed statement of the basis for the objection.

1. WHITE PAPER/PROPOSAL REVIEW PROCESS:

1. FIRST STEP – White Paper Reviews: The Government will review White Papers to identify those with the greatest potential to meet the Air Force’s needs based on the criteria above. If funding is available for an identified white paper, AFRL/RI will request a formal technical and cost proposal from the offeror. For white papers not of interest to the Government, or for which funding is not available, those offerors will receive letters from the Government indicating the basis for non-selection.

1. SECOND STEP – Proposal Review and Selection Process

a) Categories: Based on the evaluation, proposals will be categorized as Selectable or Not Selectable (see definitions below). The selection of one or more offerors for award will be based on the evaluation, as well as importance to agency programs and funding availability.

1. Selectable: Proposals are recommended for acceptance, if sufficient funding* is available.

2. Not Selectable: Even if sufficient funding existed, the proposal should not be funded.

* Selectable proposals will be designated as funded or unfunded. Letters will be sent to the unfunded offerors. These proposals may be funded at a later date without reevaluation, if funding becomes available.

b) The Government reserves the right to award some, all, or none of the proposals. When the Government elects to award only a part of a proposal, the selected part may be categorized as Selectable, though the proposal as a whole may not merit such a categorization.

c) Proposal Risk Assessment: Proposals’ technical, cost, and schedule risk will be assessed as part of the above evaluation criteria’s application. Proposal risk relates to the identification and assessment of the risks associated with an offeror's proposed approach as it relates to accomplishing the proposed effort. Tradeoffs of the assessed risk will be weighed against the potential scientific benefit. Proposal risk for schedule relates to an assessment of the risks associated with the offeror's proposed number of hours, labor categories, materials, or other cost elements as it relates to meeting the proposed period of performance.

d) Prior to award of a potentially successful offer, the Contracting Officer will make a determination regarding price reasonableness and realism.

3. FEDERAL AWARDEE PERFORMANCE AND INTEGRITY INFORMATION SYSTEM (FAPIIS) PUBLIC ACCESS: The Government is required to review and consider any information about the applicant that is in the FAPIIS before making any award in excess of the simplified acquisition threshold (currently $250,000) over the period of performance. An applicant may review and comment on any information about itself that a federal awarding agency previously entered. The Government will consider any comments by the applicant, in addition to other information in FAPIIS in making a judgment about the applicant's integrity, business ethics, and record of performance under federal awards when completing the review of risk posed by applicants as described in 2 CFR § 200.205 Federal Awarding Agency Review of Risk Posed by Applicants and per FAR 9.104-6.

4.ADEQUATE PRICE COMPETITION: As this BAA is an Open BAA, adequate price competition is not anticipated since there is no set response time, and proposals are evaluated at the time of receipt. Offerors whose proposals are selected for award will be expected to submit certified cost and pricing data on contracts exceeding $2M.

VI. STEP TWO INFORMATION – REQUEST FOR PROPOSAL & AWARD:

1. PROPOSAL FORMATING: When developing proposals, reference the AFRL "Broad Agency Announcement (BAA): Guide for Industry," Mar 2015, and RI-Specific Proposal Preparation Instructions, Dec 2020, which may be accessed at: https://beta.sam.gov/opp/e628c811fafe041accdddf55fb8539bf/view?keywords=AFRL-BAA-GUIDE&sort=-relevance&index=&is_active=true&page=1 . Always reference the newest versions of these documents.

Please note that less than 12 point font is acceptable for graphics and illustrations (as in labels and short descriptions) as long as it is readable when printed out on standard 8x11 paper.

2. AWARD NOTICES: Those white papers found to be consistent with the research areas of interest and expected results within the broad topic areas as described in the Technology Requirements section of this BAA and of interest to the Government may be invited to submit a technical and cost proposal. Notification by email or letter will be sent by the TPOC. Such invitation does not assure that the submitting organization will be awarded a contract. Those white papers not selected to submit a proposal will be notified in the same manner. Prospective offerors are advised that only Contracting Officers are legally authorized to commit the Government. All offerors submitting proposals will receive notification of their evaluation results within 45 days of submission. Offerors should email the TPOC and the Contracting Officer listed in Section VII, for status of their proposal after 45 days, if no such correspondence has been received.

3. DEBRIEFINGS: If a debriefing is requested in accordance with the time guidelines set out in FAR 15.505 and 15.506, a debriefing will be provided, but the debriefing content may vary to be consistent with the procedures that govern BAAs (FAR 35.016). Debriefings will not be provided for white papers.

4. ADMINISTRATIVE AND NATIONAL POLICY REQUIREMENTS:

1. FACILITY CLEARANCE. Depending on the work to be performed, the offeror may require a SECRET to TOP SECRET/SCI facility clearance and safeguarding capability; therefore, personnel identified for assignment to a classified effort must be cleared for access to SECRET to TOP SECRET/SCI information at the time of award. In addition, the offeror may be required to have, or have access to, a certified and Government-approved facility to support work under this BAA.

1. EXPORT CONTROL LAWS. Awards made under this solicitation may require access to, or generation of, data subject to export control laws and regulations. Only contractors who are registered and certified with the Defense Logistics Information Service (DLIS) and have a legitimate business purpose may participate in this solicitation. For questions, contact DLIS on-line at http://www.dla.mil/HQ/InformationOperations/LogisticsInformationServices.aspx or at the DLA Logistics Information Service, 74 Washington Avenue North, Battle Creek, Michigan 49037-3084, and telephone number 1-800-352-2255 (24/7). You must submit a copy of your approved DD Form 2345, Militarily Critical Technical Data Agreement, with your white paper/proposal.

1. SMALL BUSINESS PARTICIPATION. The Government encourages the best sources from the scientific and industrial communities to propose, including small business concerns, large businesses, academia and non-profit entities. Non-small business concerns are encouraged to team with small business concerns to come up with the best technical solutions and obtain the best mix of cost, performance and schedule.

1. ACTIONS FOR THE PROTECTION OF INTELLECTUAL PROPERTY, CONTROLLED INFORMATION, KEY PERSONNEL AND CRITICAL…