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

                              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

1. Part II, Full Text Announcement:

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

1. Part II, Full Text Announcement:

1. 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. 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 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 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 No. 1 to BAA FA8750-19-S-7001

The purpose of this amendment is to:

    1) Part I, Overview Information is updated to revise the types of instruments that may be awarded as shown below:

        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.

    2) Section VI.4, adds paragraphs d. and e. as shown below:

          d. ACTIONS FOR THE PROTECTION OF INTELLECTUAL PROPERTY, CONTROLLED INFORMATION, KEY PERSONNEL AND CRITICAL TECHNOLOGIES. Offerors who are requested to submit a proposal under this solicitation of grants, cooperative agreements, Technology Investment Agreements, and other non-procurement transactions only shall submit specific information for all key personnel, whether or not the individuals' efforts under the project are to be funded by the DoD. Specific requirements will be detailed in the Request for Proposal (RFP) letter. The information shall be included in the Research and Related/Key Person Profile (Expanded) form (https://www.grants.gov/forms/r-r-family.html). This collection only applies to persons identified as key personnel. This information shall not be included in the overall proposal page limits. Failure to submit this information may cause the proposal to be returned without further review, and the DoD reserves the right to request further details before making a final determination on funding an effort. This information will be used to support protection of intellectual property, controlled information, key personnel, and information about critical technologies relevant to national security. Additionally, this information will be used to limit undue influence, including foreign talent programs, by countries that desire to exploit United States' technology within the DoD research, science and technology, and innovation enterprise.

          e. BURDEN REDUCTION. With the exception of paragraph d. above, in order to reduce grant recipient reporting burden, effective 1 JAN 2019, use of the SF-424B is optional. Also, effective 1 JAN 2020, the SAM will become the central repository for common government-wide certifications and representations required of Federal grants recipients. As registration in SAM is required for eligibility for a Federal award and registration must be updated annually, Federal agencies will use SAM information to comply with award requirements and avoid increased burden and costs of separate requests for such information, unless the recipient fails to meet a Federal award requirement, or there is a need to make updates to their SAM registration for other purposes. (OMB Memorandum M 18-24).

    3) Section VI.7, adds paragraph d. as shown below:
          
    d. DFARS 252.215-7013, Supplies and Services Provided by Nontraditional Defense Contractors

    4) Revise the technical POC in SECTION VII - Agency Contacts. The TPOC is deleted in its entirety and replaced with the following:

    Frances Rose
    AFRL/RITE
    525 Brooks Road
    Rome, New York 13441-4505
    315-330-2038
    Frances.Rose@us.af.mil

    5) Section VII, updates the Alternate OMBUDSMAN as shown below:

    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.
                      Wright-Patterson AFB OH 45433-7130
                      937-904-4407
                      lisette.leduc@us.af.mil

    Alternate Ombudsman:   Mr. Steven Ewers
                                    AFRL/PK
                                    1864 4th Street
                                    Building 15, Room 225
                                    Wright-Patterson AFB OH 45433-7130
                                    (937) 255-5235
                                    Steven.Ewers@us.af.mil

    No other changes are 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: Timely, Secure, and Mission-Responsive Aerial Warfighting Network Capabilities

BAA NUMBER: FA8750-19-S-7001

PART I - OVERVIEW INFORMATION

This announcement is for an Open, 2-Step BAA which is open and effective until 29 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 3:00 PM Eastern Standard Time (EST) on 29 Sep 2023, the following submission dates are suggested to best align with projected funding:

FY19 by 18 Jan 2019
FY20 by 31 Jul 2019
FY21 by 31 Jul 2020
FY22 by 30 Jul 2021
FY23 by 29 Jul 2022

Offerors should monitor the Federal Business Opportunities website at http://www.fbo.gov in the event this announcement is amended.

CONCISE SUMMARY OF TECHNOLOGY REQUIREMENTS: This BAA is focused on the innovation, development, and maturation of secure communications, networking, and information management technologies. A timely, secure, and mission-responsive network is critical to the translation of sensory data into actionable information. The critical need is to develop affordable, extensible, interoperable communications architectures that intelligently distribute information in a robust way that enables shared situational awareness and timely decision-making, ultimately, to assure the mission.

BAA ESTIMATED FUNDING: Total funding for this BAA is approximately $500M. Individual awards will not normally exceed 36 months with dollar amounts normally ranging from $250K to $100M. 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.

ANTICIPATED INDIVIDUAL AWARDS: Multiple Awards are anticipated

TYPE OF INSTRUMENTS THAT MAY BE AWARDED: 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.

AGENCY CONTACT INFORMATION: All white paper and proposal 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):

TPOC Name:          Howard M. Beyer
Mailing Address:     AFRL/RITE
                             525 Brooks Road
                             Rome NY 13441-4505
Telephone:             (315) 330-4718
Email:                    Howard.Beyer.1@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.

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