Call_004_Skyborg_System_Design_Agent_(SDA).pdf

As of 15 October 2019

BROAD AGENCY ANNOUNCEMENT FA8650-17-S-6001

SCIENCE AND TECHNOLOGY FOR AUTONOMOUS TEAMMATES (STAT)

WHITE PAPER CALL-004 (2-STEP)

SKYBORG SYSTEM DESIGN AGENT (SDA)

This Call for White Papers is being issued under Broad Agency Announcement (BAA) FA8650-17-S-6001, which was published on FedBizOpps.gov on 7 July 2017 subsequently amended via Amendments 2 and 3. Reference FA8650-17-S-6001 and Amendments 2 and 3, which must be read in conjunction with this Call for White Papers.

THIS IS A CALL FOR WHITE PAPERS ONLY. Selection of White Papers for subsequent RFPs is subject to funding availability.

The information provided in this call for white papers is subject to change and is not binding on the United States Government (USG). AFRL has not made a commitment to issue a subsequent RFP to any of the responses, and release of this call for white papers should not be construed as such a commitment or as an authorization to incur cost for which reimbursement would be required or sought. All submissions become USG property and will not be returned.

THIS WILL BE A TWO-STEP CALL:

First Step: WHITE PAPER DUE DATE AND TIME: 15 November 2019 Wright- Patterson AFB, OH 1500 Eastern Time. Only white papers are due at this time.

Second Step: PROPOSAL DUE DATE AND TIME: To be provided with the Requests for Proposal notification sent to selected offerors from White Papers considered to meet the needs of the Air Force.

NOTE: White Paper/proposal receipt after the due date and time shall be governed by the provisions of FAR 52.215-1(c)(3). It should be noted that this installation observes strict security procedures to enter the facility. These security procedures are NOT considered an interruption of normal Government processes, and proposals received after the above stated date and time as a result of security delays will be considered “late.”

Furthermore, note that if offerors utilize commercial carriers in the delivery of proposals, they may not honor time-of-day delivery guarantees on military installations. Be advised, if the U.S. Postal Service is used, this building only receives U.S. Postal Mail twice a week and delivery by that means may not meet the proposal due date and time established herein. Early white paper/proposal submission is encouraged. Electronic submittals are preferred. Refer to the submittal instructions below for specific electronic submittal instructions.

Type of Contract/Instrument: The Air Force reserves the right to award the instrument best suited to the nature of research proposed. Accordingly, the Government may award any appropriate contract type under the FAR or Other Transaction (OT) for Prototype, grant, cooperative agreement, or OT for Research. The Air Force may also consider award of an appropriate technology transfer mechanism if applicable. It is anticipated that awards under this Call will be Other Transaction(s) for Prototype (OTP) (10 U.S.C §2371b) with cost type (with fee) payable milestones. Cost reimbursement contracts and cost type OTPs require a successful offeror to have an accounting system considered adequate for tracking costs applicable to the contract or OTP.

NOTE: If proposing a Federal Acquisition Regulation (FAR) based contract, the FAR clause references in this Call shall apply. This Call incorporates FAR and supplement provisions and clauses by reference. The full text of these provisions and clauses can be found at http://farsite.hill.af.mil. If proposing an Other Transaction (OT) pursuant to 10 U.S.C. 2371b, these FAR references and clauses would not apply. The terms and conditions of an OT agreement should be developed and negotiated on a case-by-case basis.

Potential for Follow-On Production: 10 U.S.C §2371b authorizes DoD to structure OTPs with potential to award a follow-on, sole source production contract or transaction to the OTP participant(s). Two criteria must be met to use this authority; 1) competitive procedures were used to select OTP participant(s) and 2) the participant(s) must have successfully completed the prototype project provided for in the transaction. In accordance with 10 U.S.C. § 2371b(f), the parties will consider this agreement successfully completed upon final acceptance of the prototype by the Government. Assuming successful completion of a prototype under this transaction, there exists potential for a follow-on, sole source contract or transaction, subject to a valid Government requirement and availability of funds.

To ensure no conflict of interest and focus the SDA on delivering a “Best of Breed” product to the government, it is the USG’s expectation the SDA will not be a prime competitor on a follow-on Skyborg integrated production system. Therefore, the Skyborg SDA is restricted from follow-on prime vendor contracts for the Skyborg system unless negotiated otherwise as part of this SDA effort. However, this restriction does not extend to a future SDA sub-contractor role or to the SDA subcontractors as part of a Follow-on Skyborg Production effort. See SDA Concept definition below for additional details on this restriction.

Prototypes completed as part of this project may be eligible for potential Follow-On Production under §2371b. As the Skyborg SDA is restricted from follow-on prime vendor contracts, competition is considered satisfied at the subcontractor level. Skyborg SDA subcontractors therefore would be considered participants under this transaction.

Estimated Program Cost: At this time the Air Force has allocated $7.15M as the FY2020 increment of funding. Proposals should not be restricted to this amount, but rather should address the requirements of the For Official Use Only (FOUO) Supplement Skyborg System Design Agent Statement of Objectives (SOO) (discussed further below). Rough Order Magnitude estimates provided in white papers will assist the Air Force in finalizing estimated program costs for all phases. Refer to the FOUO Supplement for a description of work scope anticipated by program phases.

http://farsite.hill.af.mil/

Note: Per section 10 U.S.C §2371b(c)(1), a Prototype OT that provides for payments in a total amount in excess of $5 million must include a clause/article that provides the Comptroller General of the United States, or an authorized representative of the Comptroller General, access to and right to examine any of the Awardee’s directly pertinent records involving transactions related to this Award. The Comptroller General of the United States, or an authorized representative of the Comptroller General, at its discretion, shall have access to and the right to examine records of any party to the Agreement or any entity that participates in the performance of this Agreement that directly pertain to, and involve transactions relating to, the Agreement for a period of three (3) years after final payment is made.

Anticipated Number of Awards: The Air Force anticipates one or more whitepapers will be selected to submit Step 2 full proposals. The Air Force anticipates one award for this announcement. However, the Air Force reserves the right to award zero, one, or more awards for all, some or none of the solicited effort based on the offeror’s ability to perform desired work and funding fluctuations.

PROGRAM SUMMARY:

The Air Force Research Laboratory (AFRL) is issuing a call for white papers under the STAT BAA to solicit industry approaches for a Skyborg System Design Agent (SDA).

The greater Skyborg program will directly support the initiatives outlined in the 2018 USAF Artificial Intelligence Strategy and the 2019 Executive Order of Maintaining American Leadership in Artificial Intelligence (AI). The Air Force has committed to executing the appropriate transition plans across resources, missions, and organizations as technology development objectives are achieved.

This Skyborg SDA effort consists of incremental program phases that correspond to the overall program goals. A detailed description of the phased SDA statement of objectives is contained in a separate For Official Use Only (FOUO) Supplement of this document (see below for the process to request the FOUO Supplement).

The objective of this call for white papers is to gauge industry interest, determine the industrial base, validate cost estimates, and solicit industry approaches to a software-centric SDA. After a review of the submitted white papers, the Skyborg program office plans to issue a formal Request for Proposal (RFP) to selected respondents as the second part of the call process. The USG anticipates one or more respondents will be notified to submit a proposal. However, the USG anticipates only one Skyborg SDA award in FY2020. Further details on the SDA concept can be found in Section I.2. of this document.

THIS IS A CALL FOR WHITE PAPERS ONLY. This document solicits approaches from US companies who have the technical expertise, experience, and interest to serve as the Skyborg SDA. Academia, DoD, or other government agencies interested in responding should contact the contracting/technical POC for instructions. It does not constitute an RFP or a promise to issue an RFP in the future. Further, AFRL is not at this time seeking proposals and will not accept unsolicited proposals. Responders are advised the U.S. Government (USG) will not pay for any information or administrative cost incurred in response to this call for white papers. Please be advised that all submissions become USG property and will not be returned. All costs associated with responding to this call for white papers will be solely at the responding party’s expense.

Small businesses are highly encouraged to provide responses to this call.

It is the responsibility of the interested parties to monitor this site for additional information pertaining to this call for white papers. This announcement is not to be construed as a formal solicitation. It does not commit the government to reply to information received, or to later publish a solicitation, or to award a contract based on this information.

All proposed products must be able to comply with the “Buy American Act” in accordance with 41 U.S.C. 10a-10d.

Please note, a FOUO Supplement containing substantial additional details and context is available to qualified US contractors, as defined by DoDD 5230.25 (which established the certified DD Form 2345, Militarily Critical Technical Data Agreement, as the mechanism for certifying qualified U.S. Contractors). For more information on establishing eligibility, please refer to DoDD 5230.25 and the Joint Certification Program, both of which can be accessed from:

http://www.dla.mil/HQ/InformationOperations/Offers/Products/LogisticsApplications/JCP.aspx

Qualified U.S. contractors must request a copy of the FOUO Supplement by contacting the Skyborg unclassified inbox (AFRL.SDPE.Skyborg@us.af.mil) and attaching a certified, current DD Form 2345. Upon confirmation of eligibility, the supplementary data package will be provided via the DoD Safe Website.

Note: Potential follow-on Requests for Proposals resulting from this call may require performers to conduct work at the TOP SECRET/Special Compartmental Information level and/or Special Access Program (SAP) levels.

Communication between Prospective Offerors and Government Representatives: Dialogue between prospective offerors and Government representatives is encouraged until submission of proposals. 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.

SUBMITTAL PROCESS:

White Papers must be submitted to the Contracting Points of Contact (POCs): Ms. Shayla Wray and Mr. Michael Wafzig, AFRL/PZLDA, Bldg 45, 2130 8th St., Wright-Patterson AFB, OH 45433-7541. Electronic submittals are preferred as described below.

Submit white papers in electronic form via the DoD SAFE file transfer service (https://safe.apps.mil/). See the steps below for details on this process.

Steps to request FOUO Supplement:

http://www.dla.mil/HQ/InformationOperations/Offers/Products/LogisticsApplications/JCP.aspx mailto:AFRL.SDPE.Skyborg@us.af.mil https://safe.apps.mil/

1.) Send an email to AFRL.SDPE.Skyborg@us.af.mil with the subject “Request Skyborg FOUO Supplement (EOM)”. Attach a certified, current DD Form 2345.

2.) The Skyborg team will respond with the encrypted FOUO Supplement via the DOD Safe website and provide a separate password to decrypt the file.

Mandatory steps to submit white papers

1.) 7-13 days prior to the submission date, send an email to AFRL.SDPE.Skyborg@us.af.mil with the subject “Request Skyborg Submission (EOM).”

2.) The Skyborg team will respond with a “Drop Off” authorization and a separate password to encrypt the submission.

3.) Submit the response via DoD Safe using the Drop Off authorization code. Encrypt the file using DoD Safe’s option and the password provided via the Skyborg team. In the short note to the recipients, place the following note:

RESPONSE TO SDPE on STAT BAA SKYBORG Call for White Papers – [Company]”

4.) The Skyborg team will respond with confirmation of receipt.

5.) For companies submitting proprietary material that will require a non-disclosure agreement for the Skyborg direct support contractors, the Skyborg team requests a separate email with the subject: “[Company] NDA Template”. Include as an attachment your company’s proposed non-disclosure agreement. Early submittal of non-disclosure agreements is highly encouraged to allow time for the documentation to be in place before submittal of white papers. As an alternative, provide a statement in your submission that the white paper can be reviewed by the Skyborg direct-support contractors.

6.) Please refer to Section IV for additional submittal information and white paper format and content guidance.

Mark proprietary information appropriately. All unclassified submissions should be marked For Official Use Only and handled IAW Department of Defense Directive 5200.1-R:

Information Security Program. If unable to utilize the DoD Safe system, contact the Skyborg team at AFRL.SDPE.Skyborg@us.af.mil and other instructions will be provided.

Responders may also send additional unclassified printed (hard) copies of their response either by certified mail or hand delivery to:

ATTN: SKYBORG PROGRAM

2241 AVIONICS CIRCLE

Room 206, BLDG 620

WPAFB, OHIO 45433-7304

Do not send classified information over an unclassified network, even if encrypted.

Classified annexes at the Secret collateral level may be sent to USAF.Wright- Patt.AFMC.mbx.AFRL-SDPE-Skyborg@mail.smil.mil. Classified responses may also be sent via regular mail. Classified mail should be double wrapped IAW [DoD 5220.22-M, Chap. 5, Sec. 4] and addressed as follows:

mailto:afrl.sdpe.Skyborg@us.af.mil https://safe.apps.mil/ mailto:afrl.sdpe.Skyborg@us.af.mil mailto:AFRL.SDPE.Skyborg@us.af.mil mailto:USAF.Wright-Patt.AFMC.mbx.AFRL-SDPE-Skyborg@mail.smil.mil mailto:USAF.Wright-Patt.AFMC.mbx.AFRL-SDPE-Skyborg@mail.smil.mil

Outer:

ATTN: DOCUMENT CONTROL

2241 AVIONICS CIRCLE

BLDG 620

WPAFB, OHIO 45433-7304

Inner:

ATTN: SKYBORG Program

2241 AVIONICS CIRCLE

Room 206, BLDG 620

WPAFB, OHIO 45433-7304

To submit a response above the secret collateral level, up to and including TS(SCI)/SAP, contact AFRL.SDPE.Skyborg@us.af.mil for instructions. Do not send classified information to this address.

mailto:AFRL.SDPE.Skyborg@us.af.mil

Full Text Announcement

I. Program Description:

The Air Force Research Laboratory (AFRL) is issuing a call for white papers under the STAT BAA to solicit industry approaches for a Skyborg System Design Agent (SDA).

1. Skyborg SDA Concept

To ensure the Skyborg system becomes a core capability for future autonomy development and not an isolated capability, the system must be designed in a way that allows rapid technology insertion, lowers the technical barriers for entry, encourages contributions from a variety of industry partners, and incentivizes rapid innovation and iterative designs as a primary means of profit. The Skyborg program office believes the best way to achieve these goals is to modularize the system into architecturally open hardware and software subcomponents through the use of a SDA.

An SDA is significantly different than a systems integrator or a contractor who performs advisory and assistance services (A&AS) for the United States government (USG).

Unlike those entities, an SDA serves as an independent organization that designs, prototypes, and tests a system with the goal of producing designs, architecture, and interfaces with unlimited government data rights. An SDA is closely tied to the program office and selects, awards, and manages subcontracts to domain experts at a speed that the government cannot match. The SDA also performs the required component system engineering and programming tasks to ensure the system can transition to an operational system.

The benefits to the government of an SDA, especially for a project such as Skyborg, are numerous:

a) The SDA concept opens the design process to businesses that specialize in design and integration, but who would typically not participate in a complex production system proposal.

b) The concept allows other specialized businesses to contribute to the project, opening the possibilities for innovative technology insertion. This technology insertion can include high Technology-Readiness Level (TRL) projects from AFRL, allowing a state-of-the-art industry-government mixture that would be difficult to replicate using traditional methods.

c) Instead of stove-piped down-selects that result in an early pairing with a contractor, the SDA concept uses open architecture and robust data rights to encourage competition not only throughout the design process, but continuously, even after initial production.

d) Subcontractor and component data rights are granted only by exception and specifically authorized by the USG prior to establishing any contractor relationship.

The USG data rights emphasis allows the government to maintain control of data rights and ensures an open architecture that will encourage future competition. The SDA, alongside the government, determines the appropriate level of data rights that protects intellectual property but maintains modularity and competition.

The SDA concept has been proven on numerous programs to incentivize collaboration and modularity while providing government-owned intellectual property.

As stated earlier in this Call, to ensure no conflict of interest and focus the SDA on delivering a “Best of Breed” product to the government, it is the USG’s expectation the SDA will not be a prime competitor on a follow-on Skyborg integrated production system. Therefore, the Skyborg SDA is restricted from follow-on prime vendor contracts for the Skyborg system unless negotiated otherwise as part of this SDA effort. However, this restriction does not extend to a future SDA sub-contractor role or to the SDA subcontractors as part of a Follow-on Skyborg Production effort. Therefore, prototypes completed as part of this project may be eligible for potential Follow-On Production under §2371b. The SDA should identify anticipated data rights as part of the white paper submittals. The SDA will assert data rights at the time of proposal, and provide the USG with any vendor data assertions for USG concurrence before subsequent vendor contract awards. The USG anticipates working with major vehicle platform providers as part of this effort, therefore the SDA will need to establish Associate Contractor Agreements with relevant vehicle platform providers.

2. Description of Skyborg Technical Area(s): This information is available in the FOUO Supplement.

3. Skyborg SDA Focus Areas: This information is available in the FOUO Supplement.

4. (Title withheld) This information is available in the FOUO Supplement.

5. Within Scope Modifications: Potential offerors are advised that due to the inherent uncertainty of research and development efforts, awards resulting from this announcement may be modified during performance to make within scope changes.

6. Deliverable Items:

a) Data Items: To be defined as part of the RFP

b) Software: To be defined as part of the RFP

c) Hardware: To be defined as part of the RFP

d) Other: To be defined as part of the RFP

7. Schedule:

a) Overall effort: To be defined as part of the RFP

b) Data Items: To be defined as part of the RFP

c) Software: To be defined as part of the RFP

d) Hardware: To be defined as part of the RFP

8. Other Requirements:

a) This announcement incorporates FAR and supplement provisions and clauses by reference. The full text of provisions and clauses can be found at https://farsite.hill.af.mil/ and https://acquisition.gov.

b) Program security classification: The current classification level is SECRET.

However, offerors MAY be required to conduct work at the TOP SECRET/ Special Compartmental Information and/or Special Access Programs levels during performance. Offerors must verify their Cognizant Security Office information is current with Defense Security Service (DSS) at www.dss.mil.

c) OPSEC: General Operations Security (OPSEC) procedures, policies and awareness are required in an effort to reduce program vulnerability from successful adversary collection and exploitation of critical information. OPSEC will be applied throughout the life cycle of the contract. While working on the government installation, OPSEC guidance and OPSEC training will be provided by the AFRL Information Protection Office. This training will ensure contractors are familiar with AFRL’s OPSEC Plan as it pertains to their contract. The contractor shall apply OPSEC in their management of their current program IAW AFI 10-701 Operations Security and WPAFB Supplement to AFI-10-701.

d) Export Control: Information involved in this research effort is anticipated to be subject to Export Control (International Traffic in Arms Regulation (ITAR) 22 CFR 120-131, or Export Administration Regulations (EAR) 15 CFR 710-774). If subject to export control, then a Certified DD Form 2345, Militarily Critical Technical Data Agreement, will be required to be submitted with proposal.

e) Export-Controlled Items: As prescribed by DFARS 225.7901-4, DFARS 252.225-

7048, “Export-Controlled Item (JUN 2013)” is contained in this solicitation. This clause shall be contained in ALL resulting contracts.

9. Other Information:

a) Government Furnished Property (GFP) availability: A list of GFP (if any), will be provided as part of the RFP. Offers shall identify any anticipated GFP as part of the proposal. Government Furnished Information (GFI) is addressed in the FOUO Supplement.

b) The contractor is responsible for all costs related to making the property available for use, such as payment of all transportation, installation or rehabilitation costs.

https://farsite.hill.af.mil/ http://www.dss.mil/

c) Base Support/ Network Access: The Air Force anticipates the SDA will need to work closely with the Skyborg program in accomplishing the contract effort. Therefore, Base Access and Network Access is anticipated during the performance of the contract effort. Potential location is Wright-Patterson Air Force Base.

d) Multiple awards subject to Fair Opportunity are not anticipated.

e) Data Rights Desired:

(1) Technical Data: Unlimited Rights

(2) Non-Commercial Software (NCS): Unlimited Rights

(3) NCS Documentation: Unlimited Rights

(4) Commercial Computer Software Rights: Customary License

*If OTPs are awarded, data rights will be specifically negotiated, but it is anticipated rights will be defined similarly to the DFARS.

The SDA, alongside the government, determines the appropriate level of data rights that protects intellectual property but maintains modularity and competition. Subcontractor and component data rights will be negotiated prior to establishing any contractor relationship. The USG data rights emphasis allows the government to maintain control of data rights and ensures an open architecture that will encourage future competition.

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

In exchange for paying for development of the data, the Government expects technical data, NCS, and NCS documentation developed entirely at Government expense to be delivered with Unlimited Rights.

Technical data, NCS, and NCS documentation developed with mixed funding are expected to be delivered with at least Government Purpose Rights. Offers that propose delivery of technical data, NCS, or NCS documentation subject to Government Purpose Rights should fully explain how the data was developed at private expense. Specifically, offers must explain what technical data, NCS, or NCS documentation developed with costs charged to indirect cost pools and/or costs not allocated to a Government contract will be incorporated, how the incorporation will benefit the program, and address whether those portions or processes are segregable.

Offerors that propose delivery of technical data, NCS, or NCS documentation subject to Limited Rights, Restricted Rights, or Specifically Negotiated License Rights will be considered. Proposals should fully explain what technical data, NCS, or NCS documentation developed with costs charged to indirect cost pools and/or costs not allocated to a Government contract will be incorporated and how the incorporation will benefit the program and whether those portions or processes are segregable.

Reference DFARS 252.227-7017, Identification and Assertion of Restrictions on the Government’s Use, Release, or Disclosure of Technical Data or Computer Software, for data rights assertion table. Data rights assertions are due at time of proposals.

Assertions must be completed with specificity. Each assertion must identify both the data and each such item, component, or process listed. Nonconforming assertions lists will be rejected.

Terms used in this section are defined in the clauses at 252.227-7013, Rights in Technical Data-Noncommercial Items, and 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation.

THIRD PARTY SOFTWARE (COMMERCIAL AND NONCOMMERCIAL):

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.

Any third party software to be delivered to the Government that are not reasonably identifiable at proposal submission, must still be approved by the contracting officer prior to incorporation into a system deliverable. This obligation to obtain pre-approval by the contracting officer, as described above, continues throughout contract administration.

The Government will neither accept nor execute a DD Form 250 for the software deliverables until the Contractor obtains from all third party software suppliers and/or vendors (Licensor) licenses that comply with the following terms and conditions for the Government (Licensee):

1. The license shall not subject the Government to liability that is indefinite or indeterminate, such as an indemnification clause, as it would constitute an obligation in advance or in excess of an appropriation and violate the Anti- Deficiency Act.

2. The license shall not create a contingent liability for the Government. This includes, but is not limited to: unilateral price increases, automatic assessment of charges, and automatic renewal of the license.

3. The license shall be governed by Federal Statutes, Case Law, and Federal Regulations, and shall not be subject to the laws or jurisdiction of any municipality, state, or foreign country.

4. The license shall not include non-substitution language that would preclude or limit the Government from using another vendor/reseller and/or product to fulfill Government requirements.

5. The license shall not comment on entitlement to attorney fees.

6. The Licensor shall not have the authority to unilaterally terminate the license.

All remedies available shall be consistent with the Disputes Clause in the underlying basic contract.

7. The Licensor shall not have the right to enter the premise or monitor the networks of Licensee for the purpose of auditing the use of the license.

8. The Licensor shall not use any injunctive relief clauses as the Licensor cannot prevent the Licensee from performing mission operations.

9. The Licensor shall not have the authority to control any litigation between a third party and the Licensee.

10. The Licensor shall not use the fact that the Licensee is using the Licensor's products in any notification to the public (e.g., no publicity rights permitted).

Additionally, the Contractor may be required to obtain licenses that comply with the following terms and conditions, based on the Government’s needs:

1. [IF APPLICABLE] The license shall not disclaim all warranties through use of an

“as is” provision.

2. [IF APPLICABLE] The license shall neither restrict the Government from using the product at various sites nor limit use of the product by various Government agencies or third parties performing work on behalf of the Air Force under the Skyborg SDA. In performance of the Skyborg SDA, Government personnel as well as Government contractors may use the software.

3. [IF APPLICABLE] [The license shall not limit the Government’s use of the software at other Government and Government contractor sites.] [The license shall authorize the Government to use the software at the following sites: [TBD]].

4. [IF APPLICABLE] The license shall not require automatic updates or give Licensor the authority to unilaterally replace the software.

5. [IF APPLICABLE] The Licensee shall not be restricted from copying or embedding elements of accessible code into other applications (e.g., nesting code, derivative works).

The Contractor may obtain agreement from the Licensor to insert the clause below to its respective software licenses intended to be transferred to the Government:

“In the event that any of the provisions of the [Software License] are determined to be inconsistent with Federal law and/or do not otherwise satisfy the Government's needs, the parties to the [Software License] hereby agree that such provisions shall be null and void as they pertain to the Government. Specifically, the following sections are hereby deleted from the [Software License] [and/or amended as indicated below]:

[Section X: deleted; Section Y: amended as follows […]”

If the Licensor will not agree to the terms and conditions cited herein and/or as contained in DFARS 227.72, the Contractor shall retain the current license on behalf of and for the benefit of the US Government if permissible under its license and such use will not subject the Government to the terms of the license.

The Contractor shall provide documentation to clearly correlate or map software license(s) to:

a) Contract Line Item Numbers (CLINS) or Payable Milestones;

b) Contracted Deliverables;

c) Paragraphs in the statement of work (SOW); and

d) Portions of any functional block diagrams and/or system architecture diagrams, so that it can be readily determined where certain commercial software corresponding to certain software license agreement(s) are physically located on the system to be delivered under the contract.

II. Award Information

1. Anticipated Award Date: March 2020

2. Anticipated funding: The Air Force has allocated an initial $7.15M (FY2020) for this SDA award. Total funding for FY2020 through FY2023 is to be determined. See paragraph IV.2.c.4. for additional information.

Skyborg SDA funding is subject to change due to Government discretion and availability.

Potential offerors should be aware that due to unanticipated budget fluctuations funding in any or all areas may change with little or no notice.

III. Eligibility Information

1. Eligible Offeror: This is an unrestricted solicitation. Small businesses are encouraged to propose on all or any part of a call solicitation.

2. Cost Sharing or Matching: TBD, however the Skyborg SDA award is anticipated to be a 10 U.S.C §2371b award. Please note OTPs will incorporate any necessary cost share requirements in accordance with 10 U.S.C §2371b.

3. Federally Funded Research and Development Centers: Refer to baseline FA8650-17- S-6001 (Section III. 3.)

4. Government Agencies: Refer to baseline FA8650-17-S-6001 (Section III. 4.)

5. Other:

a. Foreign participation: Foreign participation is not authorized.

b. There are no limits to the number of proposals an offeror may submit.

c. You may be ineligible for award if all requirements of this solicitation are not met on the proposal due date as identified above.

IV. White Paper / Proposal and Submission Information

1. Overview: This Announcement consists of a Two-Step Process described in detail below. White Papers/Proposals submitted shall be in accordance with this announcement. There will be no other solicitation issued in regard to this requirement.

The Government intends to evaluate white papers/proposals and award some, all, or none of the proposals received without negotiation/exchanges; however, the Government reserves the right to negotiate with those offeror(s) whose proposal is selected for funding.

ONLY WHITE PAPERS ARE BEING SOLICITED AT THIS TIME.

Offerors should be alert for any BAA amendments that may permit extensions to the white paper submission date

For additional information, a copy of the Broad Agency Announcement (BAA) Guide for Industry is located at:

http://www.wpafb.af.mil/Portals/60/documents/afrl/AFRL-broad-agency-announcement-guide.pdf?

All information received in response to this call for white papers that is properly marked “proprietary” will be handled accordingly and must be clearly marked. The USG shall not be liable for, or suffer any consequential damages for any proprietary information not properly identified.

Responses which contain information that is marked as “proprietary” will be reviewed by a team comprised of USG as well as contractor personnel hired to provide technical assistance to the USG. All members of the team will be reminded of their obligation to protect such information to the maximum extent permitted as required by the Economic Espionage Act, 18 U.S.C. 1831 et. seq., and other applicable statutes or regulations.

Additionally, USG members will be reminded of their obligations to afford protection under the Trade Secrets Act, 18 U.S.C. 1905. All contractor members are required to protect the information by the terms of their contracts. Responders are advised that employers of commercial firms under contract of the USG may be used to process responses, provide technical assistance or other administrative duties requiring access to other contractor’s proprietary information. These support contracts include non-disclosure agreements prohibiting their contractor employees from disclosing information for any purpose other than that for which it was furnished.

http://www.wpafb.af.mil/Portals/60/documents/afrl/AFRL-broad-agency-announcement-guide.pdf

2. First Step (White Paper) Instructions:

a. General: The FIRST STEP requests a white paper and a rough order of magnitude

(ROM) cost by USG fiscal year for Phases 0 through 3, with greatest fidelity on Phases 0 through Phase 2, as defined in the FOUO Supplement.

The white paper shall include a discussion of the nature and scope of the research and the offeror’s proposed technical approach. The Government will evaluate the white papers in accordance with the FIRST STEP evaluation criteria, set forth in Section V below. Based on this evaluation, the Government will determine which of them have the potential to best meet the Air Force’s needs.

Offerors will be notified of the disposition of their white paper. It is anticipated that Government review of the white papers submitted will take 7-10 working days. Those offerors submitting white papers assessed as meeting Air Force needs will be asked to submit a technical and cost proposal. Those offerors not requested to submit a technical and cost proposal will be notified. The Air Force will only evaluate technical and cost proposals from requested offerors. Technical and cost proposals from offerors that were not notified to submit will not be evaluated.

An offeror submitting a proposal without first submitting a white paper will not be eligible for an award.

The cost of preparing white papers in response to this Solicitation is not considered an allowable direct charge to any resulting award; however, it may be an allowable expense to the normal bid and proposal indirect cost as specified in FAR 31.205-18.

b. Page Limitation: The White Paper shall be limited to 2 pages for coversheets and front matter and 15 pages maximum for content, prepared and submitted in Word format. Font shall be standard 12-point business font Times New Roman. Character spacing must be “normal,” not condensed in any manner. Pages may be single-spaced (must use standard single-space function in Microsoft Word), double-sided (each side counts as one page), 8.5 by 11 inches, with at least one-inch margins on both sides, top and bottom. All text, including text in tables and charts, must adhere to all font size and line spacing requirements listed herein. Font and line spacing requirements do not have to be followed for illustrations, flowcharts, drawings, and diagrams. These exceptions shall not be used to circumvent formatting requirements and page count limitations by including lengthy narratives in such items. Pages shall be numbered starting with the cover page being Page 1, and the last page being no greater than Page

17. The page limitation covers all information including indices, photographs, foldouts (counted as 1 page for each 8.5 by 11 portion) tables, charts, appendices, attachments, resumes, etc. The Government will not consider pages in excess of these limitations.

Electronic submittals are preferred and should follow the process as described in the Submittal instructions located in introduction area of this document. Offerors may submit 1 original and 2 hard copies of the White Paper via mail to the

Contracting POC, identified in the Overview Information. A CD with the WORD version of your White Paper must be submitted with the hard copies of the White Paper, and must match the hard copy.

c. Format: The white paper will be formatted as follows:

(1) Section A (Coversheets and Front Matter) (2 pages maximum): BAA Number, Title of Program, Name of Company, Business Size, Company’s Commercial and Government Entity (CAGE) number, Dun & Bradstreet (D&B) Data Universal Numbering System (DUNS) number, Contracting POC and Technical POC with appropriate telephone numbers, fax numbers, email addresses for the company POCs, mailing address, and overnight delivery address (if different from mailing address). Include SIPRNET email addresses if available.

For classified submissions, also include the following information: Classified level at which company is cleared, contactor address for forwarding classified material (name, address, zip code), cognizant security office (name, address, zip code), and the name and telephone number of the offeror’s security officer. See the introduction section for detailed instructions regarding classified submittals.

(2) Section B: Period of Performance and Task Objectives (Section B, C, and D combined maximum 15 pages)

a) Include anticipated milestones and deliverables.

b) Approach to accomplishing the Skyborg SDA objectives in FOUO

Supplement and relevant experience in accomplishing similar SDA activities.

c) Approach for satisfying 10 U.S.C. §2371b OTA requirements for non-traditional vendors or for traditional defense contractors.

d) Anticipated schedule for accomplishing the SOO objectives as listed in FOUO

Supplement. The schedule should include at a minimum, anticipated effort, meetings, design reviews, major deliverables and milestones, and any other information relevant to the program effort. Of particular interest is an anticipated schedule for meeting the objectives of Phase 0 through Phase 2.

e) Anticipated manning and resources needed to accomplish the effort by phase.

This anticipated manning level should include skill sets, experience, and any special conditions required to accomplish the effort. Note: to accomplish the integrated teaming efforts necessary for a successful program, significant interaction with the USG team is expected. Therefore the SDA should consider providing one or more members of their team to be co-located with the USG at Wright Patterson AFB, Ohio in classified facilities.

f) This information is available in the FOUO Supplement.

(3) Section C: Technical Summary and Proposed Deliverables

a) Please address the following areas in your response after reviewing the specific SOO for the Skyborg SDA listed in FOUO Supplement.

b) A description of the approach to address the focus areas lists in Section I.3.

and any relevant work conducted in these areas.

c) General risk assessment of the effort and your approach to mitigating these risks.

(4) Section D: Cost of Task (Rough Order of Magnitude (ROM))

a) Include a Rough Order of Magnitude (ROM) of anticipated costs by Phase and by USG fiscal year (as listed in the FOUO Supplement).

b) The Air Force has allocated $7.15M for the initial FY2020 SDA award. The Air Force requests respondents clearly state what portions of Phase 0 (and potentially portions of Phase 1) work scope will be accomplished with the initial FY2020 $7.15M funding. Additionally, please prioritize work scope in Phase 0 (and potentially Phase 1) which will not be accomplished under the initial funding amount for USG assessment (i.e. an unfunded priority list by

FY).

c) Note: If selected for a detailed RFP, a detailed cost estimate will be required for Phase 0 through Phase 1, as well as an updated ROM for Phases 2 and 3.

d. Technical Portion: The technical portion of the white paper shall include a discussion of the nature and scope of the research and the offeror’s proposed technical approach/solution. It may also include any proposed deliverables. Resumes, descriptions of facilities and equipment, a proposed Statement of Work are not required at this point.

e. Cost Portion: No detailed price or cost support information should be forwarded; only a time-phased bottom line figure should be provided.

f. Other Information: 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 52.215-1(e).

g. White Paper/Proposal Content Summary: You may be ineligible for award if all requirements of this solicitation are not met on the proposal due date.

3. Second Step (Proposal) Instructions: NOTE: The following information is provided for awareness of proposal expectations. The Air Force will specifically notify offerors for a request to submit a proposal. Additionally, the below information is subject to change. DO NOT SUBMIT PROPOSALS AT THIS TIME.

a. General Instructions:

(1) The SECOND STEP consists of offerors submitting a technical and cost proposal currently planned to be within 30 calendar days of the proposal request.

After receipt, proposals will be evaluated in accordance with the award criteria in Section V. below. Proposals will be categorized and subsequently selected for negotiations.

(2) Offerors should apply the restrictive notice prescribed in FAR 52.215-1(e) Instructions to Offerors—Competitive Acquisition. Offerors should consider proposal instructions contained in the Broad Agency Announcement (BAA)

Guide for Industry, which can be accessed on line at http://www.wpafb.af.mil/Portals/60/documents/afrl/AFRL-broad-agency-announcement-guide.pdf? This guide is specifically designed to assist the offeror in understanding the BAA proposal process.

(3) Technical/management and cost/business volumes should be submitted in separate volumes and must be valid for 180 days.

(4) Proposals must reference the announcement number FA8650-17-S-6001, Call 004.

(5) Offerors must submit one-original and two hard copies of their proposals to the Contracting POC. Specific submittal guidance for proposal submittals will be included as part of the RFP.

(6) Offerors must include two (insert applicable number) CDs in Microsoft Office or Adobe format containing all electronic versions of required submittals. All electronic versions must match the hard copies.

a) The cost file(s) spreadsheets must be in Microsoft Excel and include the formulas for calculating cost element bases (i.e., G&A, O/H, etc.)

b) The CDs should be labeled with the company name and proposal title.

(7) Offerors are advised that only Contracting Officers are legally authorized to contractually bind or otherwise commit the Government.

(8) The cost of preparing proposals in response to this BAA is not considered an allowable direct charge to any resulting or any other contract; however, it may be an allowable expense to the normal bid and proposal indirect cost as specified in

FAR 31.205-18.

(9) Classified technical proposals or cost volumes may be submitted as part of the RFP. Offerors are encouraged to keep all elements of the proposal package unclassified. In the rare case where an offeror has a need to submit a classified appendix, please follow the classified delivery instructions in the introduction section. Classified submittal instructions will also be included as part of the RFP

b. Technical/Management Proposal:

(1) Page Limitations: The following describes proposal page limitations:

a) There is no established Technical/Management Proposal page limitation at this time. Technical/Management proposals and Statements of Work must be provided in Microsoft Word. Signed pages may be submitted in Adobe.

b) Font shall be standard 12-point business font Times New Roman.

c) Character spacing must be “normal,” not condensed in any manner.

d) Pages may be single-spaced (must use standard double-space function in

Microsoft Word), double sided (each side counts as one page), 8.5 by 11 inches, with at least one-inch margins on both sides, top and bottom.

e) All text, including text in tables and charts, must adhere to all font size and line spacing requirements listed herein. Font and line spacing requirements do not have to be followed for illustrations, flowcharts, drawings, and diagrams.

These exceptions shall not be used to circumvent formatting requirements and page count limitations by including lengthy narratives in such items.

f) Pages shall be numbered starting with the cover page being Page 1, and the last page being no greater than Page TBD in the RFP. The page limitation covers all information including indices, photographs, foldouts (counted as 1 page for each 8.5 by 11 portion) tables, charts, appendices, attachments, resumes, etc.

g) The proposal page limit does not include the offeror’s proposed Statement of Work (SOW); however, the same formatting rules apply to the SOW, which is limited to TBD pages.

h) Please Note: The Government will check the proposal and SOW for conformance to the stated requirements. Any pages in excess of the stated page limitation after the format check will not be considered for evaluation purposes.

(2) The Technical/Management proposal(s) shall include a discussion of the nature and scope of the research and the technical approach. Additional information on prior work in this area, descriptions of available equipment, use of base support (if desired), data and facilities and resumes of personnel who will be participating in this effort should also be included as attachments to the technical proposal.

This/These volume(s) shall include a SOW(s) detailing the technical tasks proposed to be accomplished under the proposed effort and suitable for contract incorporation. Do not include any proprietary information in the SOW. Refer to the BAA Guide for Industry referenced above to assist in SOW preparation. In addition to the contractor proposed SOW, a Government generated SOW attachment containing additional contracting requirements will be included in any resulting contracts. The SOW attachment will be included as an attachment to the

RFP.

(3) Any questions concerning the technical proposal or SOW preparation shall be referred to the Contracting POC.

c. Cost/Business Proposal:

(1) Separate the proposal into a business section and cost section. Adequate price competition is anticipated.

a) If selected, a Model Contract(s) or Model OTP Agreement will be provided in a separate attachment. Note that the document awarded may include contract line items (CLINs)/clauses/articles in addition to those in the model(s), and/or some of the CLIN/clauses/articles in the model(s) may be deleted, depending on the specific circumstances of the individual award. Any additions or deletions will be negotiated with the offeror prior to award.

b) The business section should contain all business aspects to the proposed contract, such as type of contract, any exceptions to terms and conditions of http://www.afrl.af.mil/contract/default.htm the announcement including the model contract, any information not technically related, etc. Provide rationale for exceptions.

c) Associate Contractor Agreements: Associate Contractor Agreements (ACAs) are agreements between contractors working on Government contracts that require them to share information, data, technical knowledge,…