FA8750-18-S-7002_FBO_FULL_TEXT.docx

ATTACHMENT I - PART II – FULL TEXT ANNOUNCEMENT

BROAD AGENCY ANNOUNCEMENT (BAA) TITLE: Capabilities for Cyber Resiliency

BAA NUMBER: BAA FA8750-18-S-7002

CATALOG OF FEDERAL DOMESTIC ASSISTANCE (CFDA) Number: 12.800 and 12.910

I. TECHNOLOGY REQUIREMENTS DESCRIPTION:

The Air Force Research Laboratory’s (AFRL’s) strategic vision for cyber superiority is to ensure the success of cyberspace-dependent missions in air, space, and cyberspace. The purpose of this BAA is to develop the next-generation technologies necessary to achieve this vision, so that they can be integrated and transitioned into warfighting capabilities.

Providing mission assurance in an Air Force context means supporting the notions of Global Vigilance, Global Reach, and Global Power across the five enduring AF core missions: air and space superiority; intelligence, surveillance, and reconnaissance; rapid global mobility; global strike; and command and control. The scope and direction of this BAA are derived from these as follows:

Global Vigilance requires continuous situational awareness and understanding across the warfighting domains. However, maintaining this awareness, which is equivalent to a pilot’s need to keep their understanding of the situation “ahead of the plane,” is impossible in an environment based on anything other than an assured and trusted infrastructure. In such an environment, most threats and attacks are avoided because of the very nature and construction of the infrastructure, not because of human operators or reactive tactics. Thus, a trusted infrastructure that is secure against attacks as well as resilient (i.e., able to recover from adverse events) is a prerequisite for the more complex, higher-level operations that achieve Global Vigilance.

An assured and trusted cyber infrastructure begins with proven-correct designs that are technologically immune to threats and have an autonomous ability to modify the cyber domain to avoid unforeseen attacks and emerging threats. With this kind of infrastructure as the foundation, additional warfighting capabilities can be instantiated. For example, the infrastructure’s intrinsic ability to avoid and be resilient to attacks can be supplemented with tried-and-true warfighting tactics such as deception, maneuver, and even deterrence.

In addition to a secure, resilient, and trusted foundation with an ability to autonomously stay ahead of the threat, the need for situational understanding, and in turn Global Vigilance, demands a complete understanding of how missions depend on the cyber infrastructure. Since mission execution is dynamic in both time and space, the ability to establish and maintain a dependency map of mission functions and threads to infrastructure must also be dynamic and resolve to continually maintain the validity of the dependency analysis.

Global Reach implies the ability to continually access and exercise command and control over warfighting forces. In the cyber domain, this applies to cyber assets supporting ongoing, as well as transient, on-demand missions deployed globally. As deployed and in-garrison cyber assets are exposed to threats, there should be contingency capabilities in the event that the infrastructure described earlier meets a threat with the potential to degrade dependent missions. These contingencies require the ability for critical slices of the infrastructure, i.e., those mapped as supporting mission essential functions (MEFs), to possess an inherent resiliency allowing them to survive the attack by re-provisioning resources to maintain the viability of designated MEFs.

When attacks degrade or destroy resources required for MEFs, the infrastructure shall have the ability to automatically maintain mission continuity by restoring, repairing, or re-provisioning critical resources.

Global Power is the ability to deliver precision effects any time, any place. In the context of cyber defense, this means using the assured and trusted infrastructure to automatically compute, provision, and deliver effects-based defenses designed to preserve missions, elicit specific desired adversary action, or provide defensive counter-cyber actions.

Technologies of interest to the strategic vision of this BAA include, but are not limited to: Cloud architectures, secure processors, virtualization, visualization, big data analysis, data mining, data fusion, novel protocols, evaluation & measurement techniques, cyber modeling & simulation, trusted hardware and software, mobile and embedded device security, standards for information exchange, risk management approaches, mathematically rigorous tools and techniques, formal methods, design frameworks, autonomy, deception, and means for recovery.

Platforms of interest to the Air Force include, but are not limited to: Military platforms and Programs of Record (POR) with cyber components or dependence, shared/commercial and private/Gov't clouds, embedded devices and firmware (BIOS, IoT), mobile and BYOD platforms, office automation systems, tactical systems, wired and wireless networks at the enterprise and tactical levels.

In addition, AFRL/RI requires research and development of assured and resilient full spectrum cyber capabilities to include cyberspace infrastructure and effects to be used in pursuit of cyber engagement and freedom of operations in cyberspace. This includes defensive technologies to strengthen the security of US cyber assets and defend against adversarial cyber advancement and cyber exploitation technologies to provide the US with intelligence regarding the cyber landscape and adversary activities in the cyber domain.

II. AWARD INFORMATION:

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

FY18 – $ 91M

a. Individual awards will not normally exceed 36 months with dollar values ranging from $200K to $3M per award. 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.

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

a. This BAA is closed to foreign participation at the Prime Contractor level.

b. Foreign Ownership, Control or Influence (FOCI) companies who have mitigated FOCI may inquire as to eligibility by contacting the contracting office focal point, Gail E. Marsh, Contracting Officer, telephone (315) 330-7518, or e-mail Gail.Marsh@us.af.mil for verification prior to submitting a white paper. Please reference BAA FA8750-18-S-7002.

c. Any performance by foreign nationals at any level (prime contractor or subcontractor) must be clearly identified in the Offerors proposal. Identify any foreign citizens or individuals holding dual citizenship expected to be involved as a direct employee, subcontractor, or consultant. For these individuals, please specify their country of origin, the type of visa or work permit under which they are performing and an explanation of their anticipated level of involvement. If a proposal is requested and selected for award, you may be asked to provide additional information during negotiations in order to verify the foreign citizen’s eligibility to participate on a contract issued as a result of this announcement.

d. 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. Any waivers to this requirement must be granted in writing by the Contracting Officer prior to providing access. The above requirements are in addition to any other contract requirements related to obtaining a Common Access Card (CAC). If 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.

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

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

b. 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 6:00 PM Eastern Standard Time (EST) on the following dates to maximize the possibility of award:

FY18 – 26 Jan 2018

White papers will be accepted until 6:00 PM EST on 30 Sept 2022, 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 Sept 2022.

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 a 4 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:

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

b. Section B: Task Objective; and

c. Section C: Technical Summary and Proposed Deliverables.

All white papers shall be double spaced with a font no smaller than 12 point. 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-18-S-7002 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 18 May 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 Security Service (DSS) Site for the NISPOM is: http://www.dss.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/RIGA 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.

Unclassified electronic submission to afrl.riga.baa@us.af.mil will only be accepted. Encrypt or password-protect all proprietary information prior to sending. Offerors are responsible to confirm receipt with the TPOC listed in Section VII. 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 2016) 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 (Oct 2016). 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, found under “ADEQUATE ACCOUNTING SYSTEM”: https://www.fbo.gov/index?s=opportunity&mode=form&id=1cffad228f48b58057072a6c9113799d&tab=core&_cview=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.

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

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

4. In addition to a local IRB approval, an AFRL-level human subjects 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.

5. 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 research areas of interest and expected results within the broad topic areas as described in the Funding Opportunity section of this BAA and of interest to the Government:

a) Overall scientific and/or technical merit including technical feasibility, degree of innovation, and understanding of the technical and operational approach for employment of the technology

b) The effort's potential contribution and relevance to the U. S. Air Force objectives

c) The extent to which the offeror demonstrates relevant technology and domain knowledge

d) Reasonableness and realism of proposed costs and fees (if any).

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:

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

b) WHITE PAPER/PROPOSAL REVIEW PROCESS:

1) FIRST STEP – White Paper Reviews: The Government will review White Papers to determine which of them have the potential to best meet the Air Force’s needs based on the criteria listed above. If white papers are of interest and funding is available, AFRL/RI will request a formal technical and cost proposal from offeror. If white papers are not of interest or there is not funding available, a letter will be sent to the offeror indicating the reason not selected.

2) SECOND STEP – Proposal Review and Selection Process

a) Categories: Based on the evaluation, proposals will be categorized as Highly Recommended, 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. Highly Recommended: Proposals are recommended for acceptance if sufficient funding is available, and normally are displaced only by other Highly Recommended proposals.

2. Selectable: Proposals are recommended for acceptance if sufficient funding is available, but at a lower priority than Highly Recommended Proposals. May require additional development. To ensure a diversity of approaches, a Selectable proposal may be prioritized over a Highly Recommended proposal if the Selectable proposal presents a unique approach unlike any of the Highly Recommended proposals.

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

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 Highly Recommended or 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 $150,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.

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, Jan 2017, which may be accessed at: https://www.fbo.gov/index?s=opportunity&mode=form&id=1cffad228f48b58057072a6c9113799d&tab=core&_cview=1. Always reference the newest versions of these documents.

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 Technical Requirements Description 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:

Depending on the work to be performed, the offeror may require a SECRET or TOP SECRET facility clearance and safeguarding capability; therefore, personnel identified for assignment to a classified effort must be cleared for access to SECRET or TOP SECRET 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.

This acquisition may involve data that is 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.

5. DATA RIGHTS:

a. SBIR RIGHTS. The potential for inclusion of Small Business Innovation Research (SBIR) or data rights other than unlimited on awards is recognized. In accordance with (IAW) the Small Business Administration (SBA) SBIR Policy Directive, Section 8(b), SBIR data rights clauses are non-negotiable and must not be the subject of negotiations pertaining to an award, or diminished or removed during award administration. Issuance of an award will not be made conditional based on forfeit of data rights. If the SBIR awardee wishes to transfer its SBIR data rights to the Air Force or to a third party, it must do so in writing under a separate agreement. A decision by the awardee to relinquish, transfer, or modify in any way its SBIR data rights must be made without pressure or coercion by the agency or any other party.

b. NON-SBIR RIGHTS.

1. Non-SBIR data rights less than unlimited will be evaluated and negotiated on a case-by-case basis. Government Purpose Rights are anticipated for data developed with DoD–reimbursed Independent Research and Development (IR&D) funding.

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

3. Third Party Software. 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.

c. IDENTIFICATION & ASSERTION. IAW DFARS 252.227-7017, the Identification and assertion of Use, Release, or Disclosure Restriction provision applies. See AFRL/RI Specific Proposal Preparation Instructions for further guidance and samples.

6. REPORTING:

a. Contract Applicable: Once a proposal has been selected for award, offerors will be given complete instructions on the submission process for the reports.

b. FAPIIS Applicable: As required by 2 CFR 200 Appendix XII of the Uniform Guidance and FAR 9.104-6, non-federal entities (NFEs) are required to disclose in FAPIIS any information about criminal, civil, and administrative proceedings, and/or affirm that there is no new information to provide. This applies to NFEs that receive federal awards (currently active grants, cooperative agreements, and procurement contracts) greater than $10,000,000 for any period of time during the period of performance of an award/project.

7. NOTICE: The following provisions* apply:

a. FAR 52.209-11, Representation by Corporations Regarding Delinquent Tax Liability or a Felony Conviction under any Federal Law

b. DFARS 252.239-7017, Notice of Supply Chain Risk

c. DFARS 252.204-7008, Compliance with Safeguarding Covered Defense Information Controls

* Please note that the current versions or deviations of the related clauses will be included in any resulting contract.

8. GRANT AWARDS ONLY: For efforts proposed as grant awards, offerors must provide an abstract in their proposal (not to exceed one page) that is publically releasable and that describes - in terms the public may understand - the project or program supported by the grant. If the proposal is selected for award, the DoD will publically post the abstract to comply with Section 8123 of the Department of Defense Appropriations Act, 2015 (Pub. L. 113-235).

VII. AGENCY CONTACTS:

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

Jeff DeMatteis

AFRL/RIGA

525 Brooks Rd Rome, NY 13441-4505 Telephone: (315) 330-7132 Email: afrl.riga.baa@us.af.mil

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

Gail Marsh Telephone (315) 330-7518 Email: Gail.Marsh@us.af.mil

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

In accordance with AFFARS 5301.91, an Ombudsman has been appointed to hear and facilitate the resolution of concerns from offerors, potential offerors, and others for this acquisition announcement. Before consulting with an ombudsman, interested parties must first address their concerns, issues, disagreements, and/or recommendations to the contracting officer for resolution. AFFARS Clause 5352.201-9101 Ombudsman (Jun 2016) will be incorporated into all contracts awarded under this BAA.

The AFRL Ombudsman and AFRL Alternate Ombudsman are as follows:

Ombudsman: Ms Lisette K. LeDuc, 1864 Fourth St.

Alternate Ombudsman: Ms Kimberly L. Yoder