FA7000-20-S-C001.pdf

COMMERCIAL SOLUTIONS OPENING (CSO)

THIS SOLICITATION IS NOT REQUESTING SOLUTION BRIEFS/PROPOSALS AT THIS

TIME

I. General Information

A. Requiring Agency Name: United States Air Force (AF) CyberWorx

B. Commercial Solutions Opening Number: FA7000-20-S-C001

C. Commercial Solutions Opening Title: AF CyberWorx Innovation Opportunities

D. Commercial Solutions Opening Type: This is the Initial Announcement

E. NAICS: 541511, Custom Computer Programming Services; 541519, Other Computer Related Services; 511210, Software Publishers; 541330,` Engineering Services; 541512, Computer Systems Design Services; 541715, Research and Development in the Physical, Engineering, and Life Sciences (except Nanotechnology and Biotechnology.

The selected NAICS will be provide in Calls.

THIS A HYBRID SOLICIATION AGAINST WHICH CALLS AND OPEN PERIODS CAN BE

RELEASED. This CSO will remain open for calls and potential open periods until 31 July 2022, to be updated annually and posted to Beta.Sam. See the full text announcement below for instructions.

II. Types of Calls

A. Calls: Three Step (See Section IV. (of the full text announcement) for Instructions): Over the period of this CSO, Calls may be issued to request solution briefs or proposals for specific Area(s) of interest (AoI). Each call will contain specific requirements and pertinent information. Solution Briefs/Pitches/Proposals submitted in response to the Calls will be accepted as specified in the individual Calls and evaluated in accordance with the Proposal Review Information (Section III.h.3. of the full text announcement). Offerors should monitor the Beta.sam.gov (previously FedBizOpps) website at https://beta.sam.gov/ for amendments to this announcement.

THREE-STEP Calls: May result in a two/three step process*

First Step: SOLUTION BRIEFS DUE DATE AND TIME: To be provided in Calls.

Second Step: PITCH SESSION DATE AND TIME: To be provided in an invite sent to offerors that submit Solution Briefs considered to meet the needs of the AF CyberWorx.

Third Step: COMMERCIAL SOLUTIONS PROPOSALS/PROTOTYPE PROPOSALS DUE DATE AND TIME: To be provided in the Requests for Proposals sent to offerors whose solution briefs AND pitch sessions are considered to meet the needs of the AF CyberWorx.

*Note: The Government reserves the right to forgo the second step and go directly to the third step.

B. Open Periods: This CSO may also have Open Periods, which will be announced via Amendments to this CSO. Solution briefs may be submitted at any time during the open period for specific AoI(s) in accordance with the instructions in the full text announcement below. Solution briefs will be reviewed and, those selected for further consideration will result in either a pitch session OR a request for proposal (RFP) letter. Proposal due dates and times will be specified in each RFP letter. Offerors should monitor the Beta.sam.gov (previously FedBizOpps) website at https://beta.sam.gov/ for amendments to this announcement.

First Step: SOLUTION BRIEF DUE DATE AND TIME: Solution briefs may be submitted at any time during the Open Period for specific AoI(s) in accordance with the instructions in the full text announcement below.

Second Step: PITCH SESSION DATE AND TIME: To be provided in an invite sent to offerors that submit Solution Briefs considered to meet the needs of the AF CyberWorx.

Third Step: COMMERCIAL SOLUTIONS/PROTOTYPE PROPOSALS DATE AND TIME: To be provided in the RFP sent to offerors whose solution briefs and pitch sessions are considered to meet the needs of the AF CyberWorx.

NOTE: Solution briefs/proposal receipt after the due date and time shall be handled in accordance with FAR 52.212-1(f). Please note: It is the responsibility of the submitting organization to ensure solution briefs/proposals have been received by the USAF Academy. If you do not receive a confirmation email within 48 hours of submitting your solution brief, it is your responsibility to contact the contracting office to ensure receipt. Failure to do so may result in a late submission.

Submission: Solution briefs and/or proposals must be submitted to the Contracting Point of Contact (POC). POC will be provided in each Call or Open Period.

III. Additional Information

Solicitation Request: Solution briefs, pitch sessions or proposals will be solicited via Calls. In addition, solution briefs may be submitted at any time during the open period. Note: Calls and Open Periods for the same AoI will not be solicited at the same time.

System for Award Management (SAM) Registration: Offerors must be registered in the System for Award Management (SAM) in accordance with FAR 52.204-7 (see https://www.acquisition.gov). SAM is the primary Government repository for prospective federal awardee information and the centralized Government system for certain contracting, grants, and other assistance related processes. It replaces CCR/FedReg, On-line Representations and Certifications (ORCA) and the Excluded Parties Lists System (EPLS). By submission of an offer, the offeror acknowledges the requirement that a prospective awardee shall be registered in the SAM database prior to award, during performance, and through final payment of any contract, basic agreement, basic ordering agreement, or blanket purchasing agreement resulting from this solicitation. Contractors may obtain information on registration and annual confirmation requirements via the SAM accessed through https://www.acquisition.gov.

Type of Award: The AF anticipates the award of commercial, Fixed Price type contracts in accordance with FAR Part 12 and the Defense Commercial Solutions Opening Pilot Program, DARS Tracking number 2018-O0016. The AF also reserves the right to award Other Transactions (OT) for Prototypes.

Nontraditional defense contractors and small businesses are encouraged to submit solution briefs or proposals under this CSO.

Definitions:

"Commercial Solutions Opening" (CSO) is a competitive procedure Contracting Officers may use to acquire innovative commercial items, technologies, or services.

"Innovative" means-

(1) any new technology, process, or method, including research and development; or

(2) any new application of an existing technology, process, or method.

"Nontraditional Defense Contractor" is defined in 10 U.S.C. § 2302(9) as an entity that is not currently performing and has not performed, for at least the one-year period preceding the solicitation of sources by the DoD for the procurement or transaction, any contract or subcontract for the DoD that is subject to full coverage under the cost accounting standards prescribed pursuant to 41 U.S.C. § 1502 and the regulations https://www.acquisition.gov/ http://www.acquisition.gov/ implementing such section. This includes all small business concerns under the criteria and size standards in 13 C.F.R. § 121.

Estimated Program Cost: It is anticipated that the cumulative amount for awards issued under this CSO will not exceed $25 million. No funding has been specifically reserved for this solicitation. Detailed estimated funding profiles will be included in Calls.

Anticipated Number of Awards: The AF anticipates making multiple contract awards; however, the AF reserves the right to award all, part, or none of an offeror’s proposal.

Overarching Program Goals: AF CyberWorx is a problem solving organization focused on human centered design that builds rapid prototypes to improve the user experience located at the United States AF Academy (USAFA) in Colorado Springs, CO. USAFA is designated as a federal laboratory, with the unique position to establish various partnerships and agreements with academia and industry, and is chartered with solving the AF’s mission problems by engaging users, industry, and academia in human centered design processes that result in solutions for the warfighter. There is interest in capturing the most creative and advanced technologies where the department can make use of defense specific projects and dual-use technologies to further its technological gain. In realizing the potential to leverage superiority in innovative technologies, AF CyberWorx endeavors to create valued partnerships by aligning itself with partners that assist in technology transfer/transition by spin-off technologies and guiding small business economic development with the primary goal of broadening the defense industrial base. This CSO is a competitive solicitation seeking proposals for innovative, commercial technologies and services that accelerate attainment of critical defense capabilities. This CSO may result in the award of prototype projects, which include not only commercially-available technologies fueled by commercial or strategic investment, but also concept demonstrations, pilots, and agile development activities that can incrementally improve commercial technologies, existing government-owned capabilities, or concepts for defense application.

AF CyberWorx is soliciting solution briefs in response to AoI(s) which will be posted as calls to this

CSO.

The CSO outlines the procedures to submit a response to an AoI to ensure a competitive process that consists of three-phases: solution brief, pitch, and full written proposal.

Communication between Prospective Offerors and Government Representatives:

Calls: Open communication between industry and Government representatives is strongly encouraged prior to the issuance of a Call. Until a Call is issued, technical and contracting questions may be resolved through open dialogue or in writing. After a Call is issued, all exchanges shall be in writing and submitted to the Contracting Officer.

If not proprietary or confidential, questions and responses, received under Calls, will be published to the Beta.sam.gov (previously FedBizOpps) website at https://beta.sam.gov/ to ensure all potential offerors are treated equitably.

Open Periods: Open communication is encouraged prior to Step-two/three under an Open Period.

Technical questions may be resolved in writing or through open dialogue until a solution brief is submitted; however, contracting questions must be in writing. After a solution brief is submitted, all communication shall be submitted to the Contracting Officer in writing.

Communications with any of the identified points of contact herein, or in a subsequent Call or CSO amendment, shall not constitute a commitment by the Government to subsequently fund or award a proposal. Only Contracting Officers are legally authorized to commit the Government.

Technical POCs:

Primary:

Michael M. Helgeson, Lt Col, USAF Deputy Director, Air Force CyberWorx michael.helgeson@edu.usafa.edu DSN: 333-3399, Commercial: 719- 333-3399

Alternate:

Ms. Jayleen Guttromson-Johnson Acquisition Program Manager jayleen.guttromson-j@usafa.edu DSN: 333-3399, Commercial: 719-333-3399

Contracting POCs:

Ms. Erica Wilson Contracting/Agreements Officer, 719-333-8048 Email address: 10CONS.PK.CyberWorx@us.af.mil

Any questions regarding this announcement shall be routed through the Contracting Office email address listed above. All questions shall be submitted in writing by email.

mailto:10CONS.PK.Cyberworx@us.af.mil

Full Text Announcement

Program Description: The United States AF CyberWorx will be soliciting solution briefs and/or technical and cost proposals through Calls or Open Periods on areas of interest (AoI) that meet the program goals listed below.

Each Call will contain specific requirements, such as the AoI and any other pertinent information. A call will be posted separately from the CSO at various times during the open period.

I. Program Goals

OVERARCHING PROGRAM GOALS: AF Cyberworx is a problem solving organization focused on human centered design that builds rapid prototypes to improve the user experience located at the United States AF Academy (USAFA) in Colorado Springs, CO. USAFA is designated as a federal laboratory, with the unique position to establish various partnerships and agreements with academia and industry, and is chartered with solving the AF’s mission problems by engaging users, industry, and academia in human centered design processes that result in solutions for the war fighter. There is interest in capturing the most creative and advanced technologies where the department can make use of defense specific projects and dual-use technologies to further its technological gain. In realizing the potential to leverage superiority in innovative technologies, AF CyberWorx endeavors to create valued partnerships by aligning itself with partners that assist in technology transfer/transition by spin-off technologies and guiding small business economic development with the primary goal of broadening the defense industrial base. This CSO is a competitive solicitation seeking proposals for innovative, commercial technologies and services that accelerate attainment of critical defense capabilities. This CSO may result in the award of prototype projects, which include not only commercially-available technologies fueled by commercial or strategic investment, but also concept demonstrations, pilots, and agile development activities that can incrementally improve commercial technologies, existing government-owned capabilities, or concepts for defense application.

II. Security

A. OPSEC: Operations Security (OPSEC) must be an integral part of our daily activities. As we maintain the security of our future technologies that are vital to our national interest, we must recognize and prepare for the threat poised against our technology. Department of Defense policies mandate a high degree of security throughout the acquisition process. However, heightened security awareness and threat-based countermeasures are particularly essential during the research and development phase when technology is most vulnerable to espionage, sabotage, or exploitation. It is the obligation of each employee or persons involved on this program to be constantly aware of and strictly adhere to security requirements designed to protect sensitive unclassified and other information and resources produced by acquisition, research and development, and technological security efforts outlined in this CSO. The contractor shall ensure employees receive training and follow appropriate Operations Security (OPSEC) measures during the performance of any resulting awards.

B. Safety: The contractor shall consider system safety requirements when developing these identified technologies/technical objectives [Ref: Military Standard (Mil-Std 882E Department of Defense Standard Practice System Safety)]. The system safety process is to identify and document any system safety hazards introduced during all phases (e.g., planning, design, fabrication and testing) and recommend adequate risk mitigations to either eliminate the identified safety risk or minimize them to an acceptable risk level. The design goal shall be to eliminate all hazards. Any residual hazards and subsequent design risk shall be summarized and provide enough detail to support an informed program management decision with regard to the design's overall safety risk. The contractor shall conduct an evaluation or assessment of these technologies and recommend appropriate system safety task(s) to be conducted in the appropriate research areas of interest.

III. Award Information

A. Within Scope Modifications: Potential offerors are advised that awards resulting from the Calls or Open Periods under this announcement may be modified during performance to make within scope changes.

B. Deliverable Items:

1. Data Items: Applicable Contract Data Requirements Lists (CDRL) will be identified in each Call and Request for Proposal (RFP).

2. Software: If applicable, specific software deliverable requirements may be included in Calls or

RFP.

3. Hardware: If applicable, specific hardware deliverable requirements may be included in Calls or

RFP.

4. Prototypes: If applicable, prototypes may be required depending on the requirements and will be identified in each Call or RFP.

5. Other: Other deliverables may be required depending on the requirements and will be identified in each Call or RFP.

C. Schedule:

1. Overall effort: Anticipated Period of Performance for awards will be addressed in each Call or

RFP.

2. Data Items: Data shall be delivered in accordance with the schedule specified in the CDRLs.

3. Software: If applicable, software delivery shall be specified in each Call or award.

4. Hardware: If applicable, hardware delivery shall be specified in each Call or award.

D. Other Requirements:

1. This announcement references the FAR and/or supplement provisions, which may be found at https://www.acquisition.gov. Offerors should familiarize themselves with the standard FAR and DFARS Part 12 provisions and clauses.

2. Program Security Classification: Security Classification will be determined for each Call/Award. If classified data will be accessed or generated, a facility and storage clearance, at the required classification level, will be required and the proposal will discuss appropriate personnel and facility clearances. Additionally, if a DD254 is applicable for a Call/Award, offerors must verify its Cognizant Security Office information is current with Defense Security Service (DSS) at www.dss.mil. Contractors are required to state in the solution brief and/or proposal the level of classification to which the contractor is currently approved. All solution briefs must be unclassified.

E. Other Information:

1. Government Furnished Property (GFP) Availability: GFP is not anticipated. However, GFP will be determined on each Call. In accordance with FAR 45.201(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.

If GFP is included in the solicitation or requested in a proposal the following clauses/provisions apply:

FAR 52.245-1 Government Property or FAR 52.245-1, Alt I in contracts other than those identified in FAR 45.104(a), or FAR 52.245-1, Alt II if the resulting contract is with a nonprofit.

2. Base Support/Network Access: Base Support/Network Access will be determined on Calls.

http://www.dss.mil./

3. Government Furnished Information (GFI): GFI will be identified in calls posted to this CSO.

4. Data Rights: Data Rights desired will be identified in calls. For additional information on Patents, Data, and Copyrights see DFARS 212.301(f)(xi) at https://www.acquisition.gov.

Offerors that propose delivery of technical data, Non-commercial Computer Software (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 severable.

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 premises 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. The license shall not disclaim all warranties through use of an "as is" provision.

2. 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 AF under the "United States AF CyberWorx Program.” In performance of the "United States AF CyberWorx Program," Government personnel as well as Government contractors may use the software.

3. The license shall not limit the Government's use of the software at other Government and Government contractor sites.

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

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

6. 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 it pertains 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 Contract Line Item Numbers (CLINS), Contract Data Requirements List (CDRLS), paragraphs in the Statement of Work (SOW), and 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.

F. Award Information

1. Anticipated Award Date: Anticipated award dates will be included in Calls.

2. Anticipated funding for the overall program is not to exceed $25 million.

This funding profile is an estimate only and not a contractual obligation for funding. All funding is subject to change at the Government’s discretion and based on availability.

Each call will have funding profiles specific to that effort. However, all offerors should be aware that due to unanticipated budget fluctuations, funding in any or all areas may change with little or no notice.

3. Award Type:

a) The AF anticipates the award of commercial, Fixed Price type contracts in accordance with FAR Part 12 and the Defense Commercial Solutions Opening Pilot Program, DARS Tracking number 2018-O0016. The AF also reserves the right to award OT for Prototypes. Nontraditional defense contractors and small businesses are encouraged to submit solution briefs or proposals under this

CSO.

b) OT for Prototype: Upon favorable review and available funds, the government may choose to award an OT for Prototype as deemed appropriate for the transaction. The Agreements Officer will negotiate directly with the offeror on the terms and conditions of the OT, including payments, and will execute the OT on behalf of the government.

Upon successful completion of a prototype project under an OT for Prototype agreement, the government and offeror may negotiate a follow-on production contract or agreement without further competition as authorized under 10 U.S.C. § 2371b(f) . Any concept/technology/solution successfully proven through an OT for Prototypes can be transitioned to production. Any resultant OT for Prototype awarded under this CSO will include language providing for the potential award of a follow-on production contract or agreement.

The AF anticipates making multiple awards. However, the AF reserves the right to award no contracts or any number of contracts for all, part, or none of the proposal(s) submitted by offerors based on the offeror's ability to perform desired work and funding availability.

Offerors are advised that the submittal of a solution brief or proposal is not a promise or guarantee of award. ONLY Contracting Officers are legally authorized to contractually bind or otherwise commit the Government.

G. Eligibility Information (Applicable to both Calls and Open Periods)

1. Eligible Offeror: This CSO is open to all small business entities and those that meet the definition of a nontraditional defense contractor.

2. Other: Foreign-Owned businesses may independently submit a solution or do so as part of a teaming arrangement with one or more United States-Owned businesses. However, the ability to obtain an agreement based upon a submission may depend upon the ability of the Foreign-Owned business to obtain necessary clearances and approvals to obtain proscribed information. If an award under this CSO involves data that may be subject to export control laws and regulations, only contractors who are registered and certified with the Defense Logistics Services Center (DLSC) and have a legitimate business purpose may participate in the solicitation. Contact the Defense Logistics Services Center, 74 Washington Avenue N., Battle Creek, Michigan 40917-3084 (1-800-352-3572) for further information on the certification process. You must submit a copy of your approved DD Form 2345, Militarily Critical Technical Data Agreement, with future proposals.

IV. Submission Information

1. Solution Briefs/Pitch Session/Proposal and Submission Information

a) Overview: Solution Briefs/Pitch Sessions/Proposals shall be submitted in accordance with this CSO, unless otherwise noted in specific calls. The Government intends to review Solution Briefs/Pitch Session/Proposals and award some, all, or none of the proposals received without negotiation/interchanges; however, the Government reserves the right to negotiate with the offeror(s) whose proposal is selected for funding.

b) First Step (Solution Brief) Instructions:

General: The FIRST STEP requests a solution brief and a rough order of magnitude (ROM) price/cost. The solution brief shall include a discussion of the nature and scope of the offeror's proposed technical approach. The Government will review the solution brief in accordance with the FIRST STEP considerations set forth below. Based on this review, the Government will determine whether the solution brief has the potential to best meet the AF CyberWorx needs. Offerors will be notified of the disposition of its solution brief. It is anticipated that Government review of the solution brief submitted will take approximately 30 calendar days. Those offerors submitting solution briefs assessed as meeting the AF CyberWorx needs as outlined in the AoI(s) may be invited to demonstrate its solution in a pitch session. Offerors whose pitch session is assessed as meeting the AF CyberWorx needs as outlined in the AoI(s) will be asked to submit a technical and price/cost proposal via letter RFP. Those offerors not requested to submit a technical and cost proposal will be notified and may request a written debriefing. Written debriefings will address only those applicable items in accordance with FAR 52.212-1(b)(l). An offeror submitting a proposal without first submitting a solution brief will NOT be considered or eligible for award. The cost of preparing solution briefs in response to this solicitation is NOT considered an allowable direct charge to any resulting contract or any other Government contract/agreement; however, it may be an allowable expense to the normal bid and proposal indirect cost as specified in FAR 31.205-18.

Page Limitation: The Solution Brief shall be limited to 5 pages (cover page not included), prepared and submitted in Word format. Font shall be standard 12 point, Times New Roman. Character spacing must be "normal," not condensed in any manner. Pages shall be single-spaced (must use standard single-space function in Microsoft Word), single-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, excluding text in tables and charts (single-spaced), 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 6. 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. Offerors should submit a Microsoft Word document of the Solution Brief via e-mail to the Contracting POC identified in the "Submission" Paragraph of the Overview Information.

Alternatively, Solution Briefs may take the form of briefing slides which should not exceed fifteen

(15) slides unless otherwise stated on the AoI. Any pages or slides submitted beyond this limitation will be removed and not evaluated.

Format: The Solution Brief will be formatted as follows:

Title Page: CSO Number, Title of Program, Area of Interest and Call number, Name of Offeror, Business Size, Offeror's Commercial and Government Entity (CAGE) number, Dun & Bradstreet (D&B) Data Universal Numbering System (DUNS) number, Contracting POC and Technical POCs with appropriate telephone numbers, and email addresses for the POCs. For proposed efforts under which classified data will be accessed or generated, add the following information: Classified level at which Offeror is cleared, contractor address for forwarding classified material (name, address, zip code), cognizant security office (name, address, zip code), and offeror's security officer's name and telephone number).

Executive Summary (one page): Provide an executive summary of the technology

Technical Concept: Describe the unique aspects of the technology and the proposed work as it relates to the AoI. Identify whether the effort includes the pilot or demonstration of existing commercial technology (identified as commercially ready and viable technology), or the development of technology for potential defense application. If development or adaptation is proposed, identify a suggested path to mature the technology. Identify aspects which may be considered proprietary.

The technical portion of the solution shall include a discussion of the nature and scope of the effort and the offeror's proposed technical approach/solution. It may also include any proposed deliverables.

Resumes, descriptions of facilities and equipment, and a proposed SOW are NOT required to be submitted with the solution brief paper.

Offeror Viability/Rough Order of Magnitude Cost/Price: Provide a brief overview of the offeror’s business establishment. Provide a ROM and a summary of current fundraising to date or a summary of the top line (gross sales/revenues). Provide a summary of product commercialization and go-to-market strategy.

Price Portion: The cost/price portion of the solution brief shall include a ROM cost/price estimate. No detailed price or cost information should be included; only a time-phased bottom line figure should be provided.

Other Information:

i. Multiple solution briefs within the purview of this announcement may be submitted by each offeror.

ii. Offerors that include in its solution brief and/or proposal data that it does not want disclosed to the public for any purpose, or used by the Government except for evaluation purposes, shall:

(1) Mark the title page with the following legend:

This solution brief/proposal includes data that shall not be disclosed outside the Government and shall not be duplicated, used, or disclosed -- in whole or in part -- for any purpose other than to evaluate this proposal. If, however, a contract is awarded to this offeror as a result of -- or in connection with -- the submission of this data, the Government shall have the right to duplicate, use, or disclose the data to the extent provided in the resulting contract. This restriction does not limit the Government’s right to use information contained in this data if it is obtained from another source without restriction. The data subject to this restriction are contained in sheets [insert numbers or other identification of sheets]; and

(2) Mark each sheet of data it wishes to restrict with the following legend:

Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposal.

iii. Solution brief Content Summary: Offerors may be ineligible for award if all requirements of this solicitation are not met on the solution brief due date.

c) Second Step (Pitch Session) Instructions*:

General: Upon review of a solution brief, the government may elect to invite the offeror to a pitch session. During this step, offerors are invited to pitch and further discuss the proposed concept/technology/solution in person or virtually.

Pitch Content: Offerors shall provide an in person (or virtual) pitch to demonstrate and provide further details on the technical and business viability of the proposed solution. In addition to the pitch, the government, at its discretion, may request an additional written submission to further supplement the information provided in the First Step solution brief.

During the pitch session, the offeror must detail/address:

Estimated Price/Schedule: Provide a ROM price and notional schedule for how this concept could be tested within the DoD.

Data Rights Assertions: The solution brief will identify any Intellectual Property (IP) involved in the effort and associated restrictions on the government’s use of that IP.

In addition to these required areas, the government may request the offeror provide additional information/detail with respect to the technology concept information provided in the solution brief.

*Note: The Government reserves the right to forgo the second step and go directly to the third step.

d) Third Step (Proposal) Instructions:

(1) General Instructions:

(a) The THIRD STEP consists of offerors submitting a technical and cost/price proposal within 30 calendar days of a RFP. After receipt, proposals will be evaluated in accordance with the award criteria in Section IV. 2. d) (3) (THIRD STEP - Proposal Evaluation Criteria, below). Proposals will be categorized and potentially selected for negotiations.

(b) Offerors that include data that it does not want disclosed to the public for any purpose, or used by the Government except for evaluation purposes, shall:

i) Mark the title page with the following legend:

This proposal includes data that shall not be disclosed outside the Government and shall not be duplicated, used, or disclosed -- in whole or in part -- for any purpose other than to evaluate this proposal. If, however, a contract is awarded to this offeror as a result of -- or in connection with -- the submission of this data, the Government shall have the right to duplicate, use, or disclose the data to the extent provided in the resulting contract. This restriction does not limit the Government’s right to use information contained in this data if it is obtained from another source without restriction. The data subject to this restriction are contained in sheets [insert numbers or other identification of sheets]; and

ii) Mark each sheet of data it wishes to restrict with the following legend:

Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposal.

(c) Title Page shall include Offeror’s name, title, point of contact name, date, e-mail address, phone, and address and any subcontractors or team members. Include an abstract which provides a concise description of the proposal.

(d) Technical and cost/business volumes should be submitted in separate volumes and must be valid for a minimum of 90 days. Subcontractor proposals must also be valid for a minimum of 90 days. No classified technical proposals or cost volumes are expected.

Offerors are encouraged to keep all elements of the proposal package unclassified. If an offeror has the need to submit a classified appendix, please contact the technical POC(s) for delivery instructions.

(e) Proposals must reference this announcement FA7000-20-S-C001; the relevant announcement Amendment number; the relevant AoI(s) and the call number.

(f) Offerors must submit an electronic copy of its proposal to the Contracting POCs email listed above. Please note: it is the responsibility of the offeror to ensure their proposal has been received by the Contracting office. If you do not receive a confirmation email within 48 hours of submission, it is your responsibility to contact the Contracting office to ensure receipt. Failure to do so may result in a late proposal. Late proposals received after the due date and time shall be government by the provisions of FAR 52.212-1(f).

(g) The cost/price file(s) must be Microsoft Office Excel spreadsheets and must include the formulas for calculating cost element basis (i.e., G&A, O/H, etc. as applicable)

Note: The cost of preparing proposals in response to this solicitation 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.

2. Technical Proposal:

a) Page Limitations: The following describes proposal page limitations:

(1) The Technical Proposal page limitations will be stated in the RFPs. Technical proposals and Statements of Work must be provided in Microsoft Word. Signed pages may be submitted in Adobe.

(2) Font shall be standard 12-point, Times New Roman.

(3) Character spacing must be "normal," not condensed in any manner.

(4) Pages shall be single-spaced (must use standard single-space function in Microsoft Word), if 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.

(5) All text, excluding text in tables and charts (single-spaced), 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.

(6) Pages shall be numbered starting with the cover page being Page 1, and the last page being no greater than Page 25. 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.

(7) The proposal page limit does NOT include the offeror’s proposed SOW (see section b) below); however, the same formatting rules apply to the SOW, which is limited to ten (10) pages.

Note: The Government will verify, upon receipt, that the proposal and SOW conform to the stated requirements. Any pages in excess of the stated page limitation will not be considered for evaluation purposes.

b) Technical Approach: The Technical proposal(s) shall describe the background and objectives of the proposed work, the approach, deliverables, and the resources needed to execute. Include the nature and extent of the anticipated results. Include ancillary and operational issues such as certifications, algorithms, and any engineering/software development methodologies to be used. The submission must include a SOW identifying the work to be performed and the deliverables. Provide a detailed project schedule that outlines the various phases of work to be accomplished within the proposed period of performance. You may refer to the solution brief that prompted this proposal request, but do not duplicate it. Provide additional details of data rights assertions that may include, but are not limited to: royalty provisions, limited licenses (scope, duration, and manner), options, conditions, right-of-first refusal, and exclusive dealing terms, amongst others. DO NOT INCLUDE ANY PROPRIETARY INFORMATION IN THE SOW. In addition to the contractor proposed SOW, a Government generated Supplemental Requirements SOW containing additional contracting requirements may be included in any resulting award(s).

Government Support Required: Identify the type of support, if any, the offeror requests of the government in general, such as facilities, equipment, data, and information or materials.

c) Price/Business Proposal:

(1) Separate the proposal into a business section and price section.

(2) In accordance with DoD Class Deviation 2018-O0016, use of a CSO is considered to be a competitive procedure for the purposed of 10 USC 137 and FAR 6.102. Additionally, the requirements of DFARS 215.371-2 do not apply to acquisitions of innovative commercial items, technologies, or services under a CSO pursuant to DoD Class Deviation 2018-O0016

(3) The business section should contain all business aspects to the proposed contract, such as type of contract (must be a firm fixed price type contract), any exceptions to terms and conditions of the announcement including any terms as applicable, any information not technically related, etc.

Provide rationale for exceptions.

(4) Identify any technical data rights being asserted (In accordance with DFARS 212.211, the DoD policy for acquiring technical data for commercial items is at DFARS 227.7102).

(5) Completed Certifications and Representations in accordance with FAR 52.212-3 (see htps://www.sam.gov and DFARS 212.301(f)(i) and https://www.acquisitions.gov).

(6) Small Business Subcontracting Plan (DoD Contracts) in accordance with 252.219-7003.

(7) If an offeror proposes the use of Government Furnished Property (GFP), other than GFP identified in an Open Period CSO Amendment or Request for Proposal, the offeror’s proposal must specifically identify each piece of GFP in the Cost/Business Proposal. Include the following information in the proposal:

(a) A list describing all Government property that the offeror or its subcontractors propose to use on a rent-free basis. The list shall identify the accountable contract under which the property is held and the authorization for its use (from the Contracting Officer having cognizance of the property);

(b) The dates during which the property will be used and, for any property that will be used concurrently in performing two or more contracts, the amounts of the respective uses in sufficient detail to support prorating the rent;

(c) The amount of rent that would otherwise be charged in accordance with FAR 52.245-9, Use and Charges; and

(d) The voluntary consensus standard or industry leading practices. and standards to be used in the management of Government property, or existing property management plans, methods, practices, or procedures for accounting for property.

(8) Cost Element Breakdown: The offeror shall submit, as a part of the price proposal, information to support the final proposed price, to include profit, i.e., uncertified cost data such as labor costs, material costs, and other direct and indirect costs. The proposed price should be broken out by Government Fiscal Year or calendar year. Any supporting schedules may include summary level estimating rationale used to generate the proposed price.

(9) If an offeror takes exceptions to the requirements called out in the announcement, the exceptions should be clearly stated in the cost/business proposal.

(10) Price/Business proposals have no page limitations.

Proposal Content Summary: Offerors may be ineligible for award if all requirements of the solicitation are not met on the proposal due date identified in the request for proposal.

d) Solution/Proposal Evaluation Information

(1) FIRST STEP – Solution Brief Evaluation Criteria: The Government will evaluate Solution Briefs to determine which of them have the potential to best meet the AF CyberWorx needs based on the following criteria, which are listed in equal order of importance:

a. Relevancy of the solution brief in addressing the AoI;

b. Technical merit of the solution in adequately addressing the government need and in the feasibility of the solution;

c. Evaluation of the Offeror’s viability and viability of the business solution;

d. Affordability (Proposed ROM Cost Estimate); and

e. Offeror’s approach is unique and/or innovative to government application.

Individual solution briefs will be evaluated against the evaluation criteria above and not against any other solution briefs held under the same AoI. If solution briefs are of interest to the AF CyberWorx, the Contracting Officer may request a Pitch session/formal technical and cost proposal from offeror.

(2) SECOND STEP –Pitch Session Evaluation Criteria: Individual pitches will be evaluated against the evaluation criteria below and not against any other pitches held under the same AoI.

Pitch submissions will be valid for 90 days after pitch evaluation. The government will aim to complete evaluation of pitches within 30 calendar days of the pitch. Upon completion of evaluations, the government will notify the offeror if it has been selected for possible award of a contract, research or prototype OT and invited to submit a full proposal; or if its proposed concept/technology/solution is not of interest to the government at this time; or if its proposed concept/technology/solution is of interest, but not eligible for a request for proposal due to available government resources. After 90 days, if government resources are not identified to formally move into the third step, the government will provide a non-eligibility notification that resources/funding is not available for the project.

Pitches shall be evaluated on the following criteria, which are listed in equal order of importance:

a. Technical merit of the solution adequately addresses the government need and is feasible;

b. Evaluation of the Offeror’s viability and viability of business solution;

c. Offeror’s approach is unique and/or innovative to government application;

d. The ROM;

e. The notional schedule is acceptable and its ability to meet the AoI need within a relevant time period; and

f. The potential impact of data rights assertions.

If pitch sessions are of interest to the AF CyberWorx and funding is available, the Contracting Officer may request a formal technical and cost proposal from offeror.

(3) THIRD STEP - Proposal Evaluation Criteria: Proposals will be evaluated through a peer or scientific review process against the criteria listed below. The following technical criteria are of equal importance:

(a) Technical:

i) Unique and innovative approach proposed to accomplish the technical objectives. New and creative solutions and/or advances in knowledge, understanding, technology, and the state of the art.

ii) The offeror's understanding of the scope of the technical effort.

iii) Soundness of the offeror's technical approach including the SOW, whether the proposal identifies major technical risks, clearly defines feasible mitigation efforts, and demonstrates related experience and qualifications of technical personnel.

iv) Realistic and/or adequacy of the proposal performance schedule

(b) Price: Price analysis will be used to determine price reasonableness in accordance with DFARS 212.209. Proposed prices of offerors will not be used for comparison purposes based on the anticipation of the submittal of meaningful proposals with varying technical and scientific approaches.

(4) THIRD STEP/PROPOSAL-Review and Selection Process:

(a) Categories: Based on the evaluation, proposals will be categorized as Highly Recommended, Selectable, or Not Selectable in accordance with the…