25-MDTF_Data Analytics Support_CSO_Call 001.pdf

FA9302-21-S-C001

Finding Agile Solutions for Test (FAST) Commercial Solutions Opening (CSO)

Call 001

“Multi Domain Test Force (MDTF) Data Analytics Support”

This Call is issued against the above referenced Commercial Solutions Opening (CSO) solicitation in accordance with DoD Class Deviation 2018-O0016 “DoD Commercial Solutions Opening Pilot

Program.”

1.0 Overview

1.1 Call Type. This is Call 001, under the FAST CSO FA9302-21-S-C001. This is a two-step closed Call, where potential industry partners provide white papers in the first step, the Air Force will review those white papers and select those that best meet the objectives described within this call. The second step is a request for full proposals, and the Air Force intends to negotiate with those industry partners.

1.2 The NAICS code associated with this requirement will be 541511, Custom Computer Programming Services, with a size standard of $34.0M.

1.3 Due date and time. White papers are due by 10 March 2025 at 11:00 AM (PST). White papers received after the due date and time shall be governed by the provisions of FAR 52.215- 1(c)(3).

1.4 Submission SPOC. White papers must be submitted to the Contracting Points of Contact (POCs):

Contracting Officer Name: Amanda Tate Address: 5 S. Wolfe Ave. Edwards AFB, CA 93524 Phone: 661-277-9466 Email: amanda.tate@us.af.mil

Contract Specialist Name: Jasmine Waterman Address: 5 S. Wolfe Ave. Edwards AFB, CA 93524 Phone: 661-277-7583 Email: jasmine.waterman@us.af.mil

1.5 Air Force Mission Owner. AFTC Det 1/MDTF, Christopher Klug

Christopher.Klug.1@us.af.mil

1.6 Type of Contract/Instrument. The Air Force reserves the right to award the instrument best suited to the nature of the solution proposed. This could be either a Federal Acquisition Regulation (FAR) based contract or an Other Transaction for Prototypes under 10 U.S.C 2371b. If an Other Transaction for Prototypes is issued, a follow-on Production contract or transaction may be issued. It is anticipated that the award under this call will be a Firm-Fixed- Price (FFP) contract.

mailto:Christopher.Klug.1@us.af.mil

1.7 Estimated Number of Awards. The Air Force anticipates awarding one (1) contract; however, the Air Force reserves the right to award zero, one, or more contracts for all, some, or none of the solicited effort based on the offeror's ability to perform the desired work and considering Air Force funding fluctuations.

1.8 Funding. Notice to Offeror(s): Funds are not presently available for this effort. No award will be made under this solicitation until funds are available. The Government reserves the right to cancel this solicitation, either before or after the closing date. In the event the Government cancels this solicitation, the Government has no obligation to reimburse an offeror for any costs.

1.9 Financing. In accordance with (IAW) FAR 32.106.

2.0 Areas of Interest:

2.1. Brief Summary.

2.2. This is a non-personnel services contract to deliver exquisite data analytics that can characterize the of Radio Frequency environments relevant to complex tests. The government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the contractor who, in turn is responsible to the government.

2.3. Background. The Multi-Domain Test Force (MDTF), in conjunction with sister services, executes test and evaluation (T&E) of complex systems in support of delivering combat-credible materiel in the context of great power competition. The Radio Frequency (RF) environment has become an increasingly important variable in the performance of complex systems and has been captured though In-Phase and Quadrature (I&Q) data recordings. The large volume and simple data format of I&Q datasets are ideal for machine learning algorithms.

Accompanying datasets from Systems Under Test (SUTs) produce smaller, denser data with several parameters. Both the RF environment characterization and the comparison of SUT data to I&Q recordings are required to extract exquisite information about SUT capabilities.

2.4. Inherently Governmental Function. The vendor shall not perform inherently governmental functions as defined in Federal Acquisition Regulation Subpart 7.5 - Inherently Governmental Functions.

2.5. Call Objectives

2.5.1. Data Models and Flows. An In-Phase and Quadrature (I&Q) and System Under Test (SUT) data model(s) and flow(s) to enable the extraction of Radio Frequency (RF) information from I&Q datasets that range from 10GBs to 1TB, and RF-related SUT parameter datasets that range from 1MB to 10GBs.

2.5.2. Radio Frequency Analytics and Visualization. Automated (AI/ML) analytical applications, based on the data models and flows, to extract RF and RF-related information. The applications will be able to extract information that includes, but is not limited to, radar pulse parametric information, communications signal characteristics, and the RF-environment for tests.

2.6. Security Requirements

2.6.1. Security Clearance Levels. The clearance level breadth of this PWS is Unclassified to Top Secret (TS), Sensitive Compartmented Information (SCI), Special Access Program (SAP). The contractor personnel performing work under this contract scopes from Unclassified to a TS/SCI and TS/SAP level security clearance at time of proposal submission. The contractor personnel must maintain the level of security required for the life of the contract. The security requirements are in accordance with the DD254.

2.6.2. Physical Security. The contractor shall be responsible for safeguarding all government equipment, information and property provided for contractor use. At the close of each work period, government facilities, equipment, and materials shall be secured. the contractor shall demonstrate compliance, in accordance with, the guidelines and security standards to protect Government information and operations as defined by the National Institute for Standards and Technology (NIST), the Federal Information Security Management Act (FISMA) and the Defense Information Systems Agency (DISA).

2.6.3. Security Requirements. Security requirements include, but are not limited to, contractor personnel performing work under this contract from Unclassified to TS/SCI and TS/SAP at time of proposal submission. The contractor personnel must maintain the level of security required for the life of the contract. The security requirements are in accordance with DD254.

2.7. Deliverables. The following paragraphs discuss deliverables expected, should an award be made for this requirement. The vendor does not need to go into detail within the white papers provided for these deliverables, but should consider the required deliverables identified below when providing the Rough Order of Magnitude (ROM) value within the white paper.

2.7.1. An I&Q data model and flow to enable the extraction of RF information from I&Q datasets that range from 10GBs to 1TB.

2.7.2. A System Under Test (SUT) data model and flow to enable the extraction of RF-related parameters that range from 1MB to 10GBs.

2.7.3. Automated (AI/ML) analytical applications to extract RF information from I&Q recordings of radars, communication systems, or the test environment.

2.7.4. Automated (AI/ML) analytical applications to extract RF-related information from SUT recordings from radars, communication systems, or the test environment.

2.7.5. Analytical and visualization applications that compare I&Q and SUT analysis and present human-digestible results.

2.8. The Air Force is interested in exploring innovative technology domains that may not be covered in the list above, the above-described area of interest is intended to also be a call for open ideas and technologies that cover other related areas not currently listed (i.e., the unknown-unknown). This Call is meant for innovative solutions to be adapted in innovative ways to meet DoD stakeholder’s needs in a short timeframe.

2.9. Communication between Prospective Industry Partners and Government Representatives. It is requested that interested industry partners submit questions in writing to the Contracting POC no later than 4 March 2025 at 4:30 PM (PST). Submitted questions will be reviewed and consolidated, and the Air Force will post answers to these questions, as an amendment to this Call by no later than 6 March 2025 at 4:30 PM (PST). Please avoid using proprietary or confidential information. If a question requires the potential industry partner to provide information that includes proprietary information, please make sure to mark the information appropriately. Discussion with any point 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.

2.10. Address questions to: Contracting Officer, Amanda Tate, e-mail amanda.tate@us.af.mil and Contracting Specialist, Jasmine Waterman, email jasmine.waterman@us.af.mil. Please include the CSO Call number in the subject line of your email.

3.0 Submission Information

3.1. First Step: White Paper Instructions

3.1.1. General. A white paper prepared in accordance with the format stated in para 3.1.3. below, shall include discussion of the nature and scope of the solution offered, the offeror’s proposed technical approach, and a rough order of magnitude (ROM) cost. The Government will review the white papers in accordance with the review criteria stated in para 4.1. Based on this review, the Government will determine which have the potential to best meet the Air Force’s needs. Offerors will be notified of the disposition of their white paper. Those offerors submitting white papers assessed as meeting Air Force needs will be asked to submit a technical and price proposal. The cost of preparing white papers in response to this announcement 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. White papers may be ineligible for further consideration if all requirements of this solicitation are not met. The White Paper should focus on the solution offered to meet the objectives identified above.

3.1.2. White Page Instructions. White papers shall be detailed (clearly demonstrate how all objectives will be accomplished) enough to allow for a limited technical evaluation and to fully understand the materials used. White papers are limited to 20 pages prepared in .pdf format. Font should be size 10 standard business font, normal character spacing (i.e., not condensed). White papers received that exceed the page limitation will have the excess pages removed before review. White papers submitted that are illegible will not receive further consideration. Include page numbers.

mailto:amanda.tate@us.af.mil mailto:jasmine.waterman@us.af.mil

3.1.3. Format. The white paper shall be formatted as follows:

3.1.3.1. Section 1. Title page

3.1.3.1.1. The white paper shall include a title page which identifies the company name, the company’s Commercial and Government Entity (CAGE) number, the company’s Dun & Bradstreet Data Universal Numbering System (DUNS) number, Company POCs (include email and telephone), and the title of the white paper. The title page does not count towards the page limitations identified above.

3.1.3.2. Section 2. Technical summary of proposed solution

3.1.3.2.1. Describe the technical summary of the proposed solution meeting the area of interest/objectives, including how the solution addresses the objectives identified in para. 2 within this Call and how the offeror intends to integrate the identified GFE items.

3.1.3.2.2. A statement of agreement to following any Associated Contractor Agreement that may be included in any resulting contract award. Additionally, a description of any projects that require collaboration with multiple contractors in a similar arrangement to an Associated Contractor Agreement.

3.1.3.3. Section 3. Estimated delivery schedule or period of performance

3.1.3.3.1. Describe the estimated lead time from award of a contract/agreement or the estimated period of performance length.

3.1.3.4. Section 4. ROM

3.1.3.4.1. The ROM is provided as a bottom-line estimate used to indicate possible magnitude of proposed solution. This is not a request for a full price proposal. The offeror may segregate pricing to fit the technical summary provided in Section 2 of the white paper (e.g., if the technical summary proposed two approaches, the offeror may provide a ROM for each). The Air Force may use this to assist in making budget related decisions. The Air Force does not intend to award based on this dollar value.

3.1.3.5. Section 5. Open discussion

3.1.3.5.1. This section is optional and can be used to cover any information the potential industry partner wishes to address.

3.1.4. Other Information. Multiple white papers within the purview of this Call 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). Offerors shall not submit white papers that contain classified information without receiving further instruction by the Contracting

POC.

3.1.5. Eligible Offeror. This is an unrestricted request. Small businesses are encouraged to submit white papers. Offerors are encouraged to complete the Annual Representations and Certification in the System for Award Management (SAM) as soon as possible.

3.1.6. There are no limits on the number of White Papers/proposals an offeror may submit.

3.1.7. You may be ineligible for award if all requirements of this solicitation are not met within the White Paper and proposal (if applicable) by the due date as identified above and in subsequent requests for proposals, if selected to provide a proposal.

3.2. Second Step. Full Proposal Requirements

3.3. PROPOSAL DUE DATE AND TIME. To be provided in the Requests for Proposal sent to offerors that submit White Papers considered to be of further interest to the Air Force.

Proposals received after specified date and time, will be considered late in accordance with 52.212-1(f).

3.4. Submission POC: Full Proposals must be submitted to the Contracting Points of Contact (POCs):

Contracting Officer Name: Amanda Tate Address: 5 S. Wolfe Ave. Edwards AFB, CA 93524 Phone: 661-277-9466 Email: amanda.tate@us.af.mil

Contract Specialist Name: Jasmine Waterman Address: 5 S. Wolfe Ave. Edwards AFB, CA 93524 Phone: 661-227-7583 Email: jasmine.waterman@us.af.mil

3.4.1. General. The Government will invite select offerors to submit full proposals based on favorable evaluation results of White Papers. Although multiple vendors may be selected to provide Proposals, due to the current area of interest the government intends to select one offeror to submit a Proposal. Proposals will be requested via a Request for Proposal (RFP) letter by the contracting officer and will contain separate submission instructions and applicable due dates and timelines. The letter RFP will identify the information required to evaluate the full proposal (e.g., technical and price volumes). At a minimum, the Air Force will evaluate responses to letter RFPs for technical and price.

Additional criteria may be required in order to adequately evaluate an offeror’s proposed approach (e.g., past performance). The letter RFP will contain other instructions such as the proposal due date, format, Air Force POCs, and submission method. The cost of preparing proposals in response to a letter RFP is not considered an allowable direct charge to any resulting contract or agreement. Unsuccessful offerors will be notified by the Government, either via email or letter, to inform them that the proposed effort is not of interest to the Government at this time.

3.4.2. Statement of Work. Each response to a letter RFP shall include a non-proprietary version of a Statement of Work (SOW). The SOW shall contain a summary description of the proposed solution, to include detailed task descriptions. This document will be made part of any resulting contract. The following is an outline for a SOW.

3.4.2.1. Background: The background information should identify the requirement in very general terms; describe why the project is being pursued, and how it relates to other projects. Summarize any statutory authority or regulations affecting the overall requirement.

3.4.2.2. Scope: This section should provide a brief statement of what the offeror expects to accomplish under the contract — the breadth and limitations of the contract effort. It should not include specific work tasks or a description of deliverable products since this will be included in the “Tasks” section.

3.4.2.3. Objectives: This section should provide a concise overview of the contract effort goals and objectives; and how the results or end products will be used.

3.4.2.4. Tasks/Technical Requirements: This section defines the tasks that the vendor shall complete during contract performance and would have a task description for each step of the Work Breakdown Schedule (WBS). The description of task requirements will depend on the approach that is selected to describe the required effort.

3.4.2.5. Deliverables: This section should clearly state all deliverables including CDRLs and material.

3.4.2.6. Period of Performance: The period of performance shall be clearly stated using units of months after contract award. Milestones shall be stated as a number of months after contract award. These milestones shall include the end of technical effort and end of contract period of performance.

3.4.2.7. Cost or Pricing Data: This Call is being executed under a CSO, which is authorized under a current Class Deviation (ref. DARS Tracking Number 2018-O0016, Class Deviation – Defense Commercial Solutions Opening Pilot Program). As such, awards made against this CSO will be considered commercial for the award itself. Awards issued outside of a CSO will require a separate determination of meeting the definition of a Commercial Item IAW FAR 2.101. Since awards made against this Call will be considered commercial, certified cost or pricing data will not be required. However, a Contracting Officer may require other than certified cost or pricing data in order to support price reasonableness.

3.4.3. Proposal Validity Period. Unless otherwise specified in the letter RFP, offerors must state the proposal validity period of their proposal. A minimum proposal validity period of 90 days should be provided.

4.0 Evaluations

4.1. White Paper Evaluation. The Air Force will review white papers as follows:

1. Technical approach to meeting the described objectives within this Call, to include how the offeror plans on integrating the identified GFP items

2. Ability to participate in the associated vendor efforts to fully integrate the required capabilities.

3. Funds Availability

4.2. White Papers will be categorized as Recommended, Selectable, or Non-selectable as follows:

1. Recommended: White papers are recommended for acceptance if sufficient funding is available and normally are displaced only by other recommended proposals.

2. Selectable: White papers are recommended for acceptance if sufficient funding is available, but at a lower priority than recommended proposals. A Selectable proposal may require additional development. To ensure a diversity of approaches, a Selectable proposal may be prioritized over a recommended proposal if the Selectable proposal presents a unique approach unlike any of the recommended proposals.

3. Not Selectable: Even if funds were available, the white papers should not be funded

4.3. The Air Force will negotiate directly with those offerors selected for funding based off the white paper evaluations described above. Awards are contingent upon successful negotiations.

The Air Force reserves the right to discontinue negotiations with any vendor should parties fail to reach agreement on contract terms, conditions, or price within a reasonable time. The Air Force may award all, some, or none of the proposed effort. Price will be considered to determine that the proposed price is fair and reasonable.

5.0 Other Information

5.1. System for Award Management Registration

5.1.1. FAR 52.204-7, System for Award Management (SAM) and DFARS 252.204-7004, Alternate A, System for Award Management (SAM) are included by reference. 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. 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. Vendors may obtain information on registration and annual confirmation requirements via the SAM accessed through https://www.acquisition.gov or by calling 866-606-8220.

5.2. Debriefings

5.2.1. The Government will conduct written, post-award debriefings upon request only in accordance with FAR 52.212-1(l) and will address the evaluation factors contained herein only. It will not include a comparison of submissions against a common statement of work (SOW) as the CSO provides no common statement of work that interested parties must respond to and instead represents opportunity for submission of a variety of innovative commercial items, technologies, and/or services that represent meaningful submissions of diverse scope and price.

5.3. Associated Contractor Agreement

5.4. Non-government advisors

5.4.1. Offerors are advised that data submitted to the Government in response to this solicitation will be released to individuals who work for the following government support contractor(s):

MTSI, and JT4

5.4.2. These contractors provide advice and assistance analyzing and reviewing acquisition documentation and participate as advisors in Government Source Selections. Offerors not wishing to have their submission released to the companies listed above must notify the Contracting POC before submission of their white paper. Please contact the Contracting POC within this Call with questions or concerns regarding their role.

5.5. Covered Defense Information

5.5.1. Offerors should take note that the provision at DFARS 252.212-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting is included in this Call. It is anticipated that contractors will not be provided or generate Covered Defense Information which will be processed, stored, or transmitted on/through an unclassified system that is owned, or operated by or for, a contractor.

5.6. Government Furnished Property (GFP) Availability

5.6.1. GFP is anticipated to be made available under any resulting contract. In accordance with FAR 45.201(b), the vendor is responsible for all costs related to making the property available for use, such as payment of all transportation, installation, or rehabilitation costs.

5.7. Other Applicable Provisions/Clauses

5.7.1. Other applicable provisions/clauses will be provided to potential industry partners within letter RFPs issued.

5.8. Marking Proprietary Proposal Information

5.8.1. Information contained in unsuccessful proposals will remain the property of the Applicant.

The Federal Government may, however, retain copies of all proposals. Public release of information in any proposal submitted will be subject to existing statutory and regulatory requirements. If proprietary information is provided by an Applicant in a proposal, which constitutes a trade secret, commercial or financial information, it will be treated in confidence, to the extent permitted by law, provided that the proposal is clearly marked by the Applicant as follows:

Proposal data the firm does not wish to make public, or to be used by the Government except for peer review, shall:

(1) Mark the first page of each proposal volume 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 pages [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 page is subject to the restriction on the first page of this volume." DoD assumes no liability for unmarked data disclosure or use and may use or disclose such data for any purpose.