Timely, Secure, and Mission-Responsive Aerial Warfighting Network Capabilities   2

Amendment No. 2 to BAA FA8750-19-S-7001
The purpose of this amendment is to:
1. Section I-TECHNOLOGY REQUIREMENTS-make updates to Focus Area 3 as shown below:

1.0 Tactical Network Security/Information Assurance

Demonstrate ability to securely share multiple forms of information (e.g., voice, video, text, files) among networks of differing classifications and releasabilities. Information exchanges are secured through a combination of data inspection to prevent data spills and propagation of cyber-attacks, data canonicalization to simplify these data inspection techniques, and novel methods to attest the provenance of trusted data in an assured manner.

Develop a more agile and robust information management capability that spans security domains, allowing for more seamless sharing with our coalition partners. The secure data sharing capability develops technologies to enable both information sharing and data exchange across multiple security domains (e.g. JWICS, SIPRNET, NIPRNET, coalition networks) and also push the state-of-the-possible in object level protection at a level commensurate with enforcing mandatory access controls on a single, multi level network.

Demonstrate a wide range of information exchange capabilities that are scalable, adaptable, secure, resilient, context-aware, federated and responsive to dynamic mission conditions and management policies. The technologies to support these capabilities include: mission-oriented architectures, Quality of Service policies, publish/subscribe/query mechanisms, semantic characterization, federation, machine learning, opportunistic resource scheduling, peer-to-peer protocols, and open system architectures.

Develop the tools necessary to provide global interoperability without global consensus with integration of DoD systems of both hardware and software using a Systems of Systems approach. New and preexisting technologies should be hosted in a wiki type knowledge base. This includes but not limited to Software as a Service (SaaS), Platform as a Service (PaaS), Infrastructure as a Service (IaaS) and Community Cloud.

Research and implement cloud-based hosting to enable information sharing which will allow a wide range of information exchange capabilities that are scalable, adaptable, secure, resilient, context-aware, federated and responsive to dynamic mission conditions and management policies.

2. Part I and Part II, Section IV.1, update the white paper due dates as follows:

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

FY19 by 18 Jan 2019
FY20 by 16 Dec 2019
FY21 by 31 Jul 2020
FY22 by 30 Jul 2021
FY23 by 29 Jul 2022
White papers will be accepted until 3 PM EST on 29 September 2023, but it is less likely that funding will be available in each respective fiscal year after the dates cited. This BAA will close on 29 September 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.

No other changes are made.

AMENDMENT 3 to BAA FA8750-19-S-7001

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, updates FBO reference to Beta SAM website;
2. Section III.2.b.2, updates the DCSA website;
3. Section IV.3.c, updates the mailing instructions;
4. Section IV.4.e, updated the link to reference the Beta SAM website;
5. Section VI.1, updates the RI Specific Proposal Preparation Instructions date and Beta SAM link;
6. Section VII: updated the OMBUDSMAN.

No other changes have been made.

________________________________________

Please see the attached for full Amendment 3 Announcement

AMENDMENT 4 to BAA FA8750-19-S-7001

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 II, Full Text Announcement:
   1. Section IV.2, updates content and format language;
   2. Section IV.3.a, updates the DCSA website;
   3. Section IV.3.c, updates the mailing instructions;
   4. Section IV.4. b and c; updates the applicable provision and clause dates;
   5. Section VI.1, updates the proposal formatting language;
   6. Section VI.4, updates the applicable provisions;
   7. Section VII: updated the OMBUDSMAN date.

No other changes have been made.

SEE ATTACHMENT FOR FULL ANNOUCEMENT DETAILS.

AMENDMENT 5 TO BAA FA8750-19-S-7001

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:
   1. Updates references of Beta SAM to SAM
2. Part II, Full Text Announcement:
3. 1. Section III, adds paragraph 4 regarding Organizational Conflicts of Interest;
   2. Section IV.3.a, updates the NISOPM reference to reflect it being codified in the CFR;
   3. Section IV.4, adds paragraph g;
   4. Section V., adds paragraph 4 regarding adequate price competition;
   5. Section VI.1, updates the Proposal Formatting language;
   6. Section VI.7, updates the applicable provisions;
   7. Section VII: updated the OMBUDSMAN

No other changes have been made.

SEE ATTACHMENT FOR FULL AMENDMENT DETAILS.

Amendment No. 6 to BAA FA8750-19-S-7001

The purpose of this amendment is to:

1. Section III, Eligibility Information, adds the following paragraph 5 for S&T Protection:

5. In accordance with AFRLI 61-113, S&T Protection, Contractors/Recipients are required to submit with their proposal a Standard Form 424, "Research and Related and Senior and Key Person Profile (Expanded), as well as a Security Program Questionnaire, which are included in the RI-Specific Proposal Preparation Instructions and can be accessed at:

https://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. Complete and submit the required forms with your proposal to the technical point of contact (TPOC) listed in Section VII-Agency Contacts AND AFRL.RIOF@us.af.mil.

Contractors will be required to provide documentation of their Security Program Plan for initial Institution S&T Protection Program Review. The purpose of requesting the plan is to evaluate the offeror's capacity for protecting the Government's S&T and failure to demonstrate a plan adequate to meet the needs of the requirement may be grounds for considering the proposal unawardable. In the event a security risk is identified and the Government has determined the security risk exceeds the acceptable threshold, the Contractor/Recipient will be notified and informed of the termination/decline of award. The Government will be only required to provide a general statement of the reasoning due to Government OPSEC measures.

After award, the Contractor/Recipient will be required to re-submit the Standard Form 424 as an annual requirement to the points of contact listed above.

No other changes are made.

AMENDMENT 7 to BAA FA8750-19-S-7001:

The purpose of this Amendment is to cancel BAA FA8750-19-S-7001.

This BAA is now closed and no further white papers will be accepted.