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:
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:
No other changes have been made.
SEE ATTACHMENT FOR FULL ANNOUCEMENT DETAILS.