Space-to-Space Comm BAA Posting_15 Sep 25_Final.pdf

BROAD AGENCY ANNOUNCEMENT (BAA)

(Solicitation FA8819-25-R-B006)

Space-to-Space Communication Technology Projects in Support of

Space Systems Command (SSC)

Space Combat Power (SCP)

Program Executive Office (PEO)

General Information:

Broad Agency Announcement (BAA) Number: FA8819-25-R-B006 BAA Type: Basic BAA with targeted calls only BAA Period of Performance (POP): 60 months beginning 15 Sep 25 and ending on 14 Sep 30 Posted Date: 15 Sep 25 White Papers for Call #1.1 Due: 12:00pm Pacific Daylight Time (PDT) 6 Oct 25 North American Industry Classification System (NAICS) code for this BAA: 541715 Research and Development, in the Physical, Engineering, and Life Sciences (except Biotechnology).

Anticipated Awards: One or more awards is anticipated for Call #1.1; however, SSC/SCP reserves the right to select for award zero, one, or more of the proposals or a portion of thereof received in response to this announcement.

Contracting Office Address:

SSC/SZK

483 N. Aviation Blvd. A-8 El Segundo, CA 90245 Points of Contacts (POCs): All communications and questions associated with this BAA shall be submitted in writing to the POCs listed below.

Contracting Officer (CO):

Mr. Robert M. Chernoff

SSC/SZK

483 N. Aviation Blvd. A-8 Telephone: (310) 653-9482 Email: robert.chernoff@spaceforce.mil

Capt Tobias J. Richards

SSC/SZK

483 N. Aviation Blvd. A-8 Telephone: (310) 653-7796 Email: tobias.richards.1@spaceforce.mil

Security POC:

Mr. Chrisopher Colon

SSC/SZ

483 N. Aviation Blvd. A-5 Email: christopher.colon.4@spaceforce.mil

Technical POC:

Maj Justin Mayfield

SSC/SZWM

483 N. Aviation Blvd. A-8 Email: justin.mayfield.7@spaceforce.mil mailto:christopher.colon.4@spaceforce.mil

Table of Contents

1 Background 5 2 Areas of Technology Project Interest 5

2.1 Focus Area 1: Space-to-space Communications 5

2.1.1 Objective 1a: Enable advancements in optical communication 5

2.1.2 Objective 1b: Create advanced data links and waveforms 5

2.1.3 Objective 1c: Novel communication techniques 6

2.1.4 Objective 1d: Enable alternate Positioning, Navigation, and Timing (PNT) 6

2.1.5 Objective 1e: Enable space hardware advancements in space-based user radios, mission antennas and information assurance/cryptographic infrastructure 6

2.1.6 Objective 1f: Enable support infrastructure for tasking and orchestration 6

2.1.7 Objective 1g: Enable RF communication payload technology maturation 6

2.1.8 Objective 1h: Enable payload hosting 7

2.2 Focus Area 2: Space Networking 7

2.2.1 Objective 2a: Enable a high-rate mesh backbone 7

2.2.2 Objective 2b: Enable seamless multi-level security (MLS) operations in contested environments 7

2.2.3 Objective 2c: Enable cyber defense 7

2.2.4 Objective 2d: Enable an enterprise hybrid architecture 7

3 BAA Structure 7

3.1 Nomenclature 7

3.2 Approach 8

3.2.1 Option 1: Two-Phase Approach 8

3.2.1.1 Phase 1: White Papers 8

3.2.1.2 Phase 2: Full Proposals 8

3.2.1.3 Notional Timeline – Two-Phase Approach 9

3.2.2 Option 2: One-Phase Approach 9

3.2.2.1 Phase 1: Full Proposals 9

3.2.2.2 Notional Timeline – One-Phase Approach 10

4 Award and Funding Information 10

4.1 Eligibility Information/Sources 10

4.2 Cost Sharing/Funds Matching 11

5 Submissions – General Information and Instructions 11

5.1 General Information 11

5.2 General Instructions 11

5.3 Availability of Equipment and Software 12

5.4 Security Classification of Submissions 13

5.5 Contract Type 13

5.6 General Award Information 13

5.7 Notifications 13

5.7.1 White Papers 13

5.7.2 Full Proposals 14

5.7.3 Debriefings 14

5.8 Use of Non-Government Advisors 14

5.9 Submission Instructions 15

5.9.1 Delivery 15

5.9.2 Late Submissions 15

5.10 Facility Clearance 15

5.11 Commitment to Small Business 16

5.12 White Paper Instructions 16

5.13 Full Proposal Instructions 17

5.14 Evaluation and Selection Information (See FAR 2.101 and 3.104) 24

5.14.1 General Information 24

5.14.2 BAA Peer Technical Review 24

5.14.2.1 White Paper Evaluation Factors 25

5.14.2.1.1 Factor #1: Contribution to Focus Area(s) and Objective(s) 25

5.14.2.1.2 Factor #2: Technical Approach 25

5.14.2.1.3 Factor #3: Cost 25

5.14.2.2 Full Proposal Evaluation Factors 25

5.14.2.2.1 Factor #1: Contribution to Focus Area(s) and Objective(s) 25

5.14.2.2.2 Factor #2: Technical Approach and Assumptions 25

5.14.2.2.3 Factor #3: Cost 26

5.14.2.2.4 Proposal Categorization 26

5.15 Data Rights and Proprietary Data 26

5.15.1 Unlimited or Government Purpose Rights 26

5.16 Government Rights Prior to Contract Award 26

5.17 Pre-Proposal Communication between Prospective Offerors and Government Representatives 26

6 Attachments 27

1 Background

Mission Space Combat Power (SCP) is the Space Systems Command (SSC) Program Executive Office (PEO) focused on developing and delivering combat power capabilities in and through space while also providing National security deterrence capabilities countering those identified threats to prevail in a space conflict. This includes acquiring, developing, and fielding resilient space capabilities to protect national interests, enable critical infrastructures, and support the warfighter. Space Combat Power was established to stay ahead of emerging threats by partnering with the defense and commercial industry, academia and allied partners to deliver cutting edge technology in support of full and continuous characterization of space, when necessary, prevailing in a multi-domain conflict extending to space. Dedicated acquisition personnel lead the way to enable and deliver next-generation space enterprise solutions through rapid, innovative, and affordable technology leveraging the full spectrum of partnerships.

Perpetual and prolific space characterization is a foundational requirement for continued, sustainable use of space. The need is even more urgent in today’s contested and congested space domain where satellites are proliferating, adversaries are demonstrating aggressive behaviors, and additional threats are emerging. These new threats necessitate dominant and resilient combat power that can gain and maintain space superiority. To that end, SSC/SCP is seeking state-of-the-art technology advancements in proliferated low Earth orbit (pLEO) for Space-to-Space Communications by soliciting technology project contracts through this BAA.

Purpose To address near-term pLEO technology challenges, the Government, through this solicitation, is seeking advancement in the following two (2) overarching areas:

1. Space-to-space communications and

2. Space Networking.

The following section on areas of technology project interest further details the intended BAA focus areas.

2 Areas of Technology Project Interest

2.1 Focus Area 1: Space-to-space Communications

2.1.1 Objective 1a: Enable advancements in optical communication Focus items can include but are not limited to: 1. interoperability and standardization of optical communications terminals capable of adapting to multiple optical inter-satellite link (OISL) standards to connect heterogeneous satellite constellations, 2. low size, weight, power, and cost (SWaP-C) optical terminals, 3. technologies for significantly increased data transfer rates, 4.

reconfigurable modems which can support a variety of optical waveforms and modulation formats, 5. improving the accuracy and robustness of pointing, acquiring, and tracking algorithms for optical terminals to establish and maintain high-speed communication links, particularly in dynamic environments and at long distances, 6. multi-orbit space data transport exchange capabilities, and 7. distributed optical ground station networks to mitigate atmospheric interference and enhance resilience.

2.1.2 Objective 1b: Create advanced data links and waveforms

Focus items can include but are not limited to: 1. data links/waveforms which operate in contested (interference) environments, 2. data links/waveforms which operate through scintillated atmosphere, “communications blackout” hypersonic plasma sheath, or in close proximity to thruster plumes, 3. data link/waveforms that provide for low probability of intercept (LPI) / low probability of detection (LPD) / low probability of geolocation (LPG) capabilities, and 4. data links/waveforms which compensate for high rate (orbital/hypersonic) relative user motion doppler effects.

2.1.3 Objective 1c: Novel communication techniques

Technical thrusts can include but are not limited to: 1. resilient and robust communications in contested and dynamic environment, 2. high data rate communications to support growing data demands, 3. interoperability and standardization across heterogeneous constellations and systems, 4. efficient and automated resource management and network control in complex space architectures, and 5. emerging technologies such as artificial intelligence (AI) / machine learning (ML), quantum communications and advanced antenna systems.

2.1.4 Objective 1d: Enable alternate Positioning, Navigation, and Timing (PNT) Focus items can include but are not limited to: 1. independence from the Global Positioning System (GPS) or other global navigation satellite system for the satellite network and supporting user equipment, 2. provisions for transmitting precise time and navigation information to tactical users, 3. ranging via optical crosslinks and radio frequency (RF) user links, 4. candidate navigation and ranging signals (waveforms), 5. low SWaP-C precision timekeeping systems, quantum inertial sensors, or other hardware or software to support alternate PNT.

2.1.5 Objective 1e: Enable space hardware advancements in space-based user radios, mission antennas and information assurance/cryptographic infrastructure Technology projects can include but are not limited to: 1. SWAP-C and performance of LINK- 182 user radios, 2. multi-waveform capabilities which address use of standards, 3. advanced use of Space Ground Link Subsystem (SGLS), 4. secure and assured communications in contested environments, and 5. LPI/LPD connectivity.

2.1.6 Objective 1f: Enable support infrastructure for tasking and orchestration The Government is seeking to enable a common, resilient ground support infrastructure necessary to allow space-based capabilities to transmit, receive, process, exploit and/or disseminate data. Fundamentally, this infrastructure must manage the constellation, host and execute tactical command and control (C2) capabilities, and task and manage ground-based communication entry/exit points. This infrastructure will need to seamlessly integrate with global operations systems and facilities, facilitate “lights out” operations, and provide for operator training.

Technology projects can include but are not limited to improving intelligent tools and techniques for: 1. managing, monitoring, and automating user support and 2. corresponding mesh network operations. The goals are to improve efficiency and reduce the need for extensive manual configuration.

2.1.7 Objective 1g: Enable RF communication payload technology maturation The Government is seeking projects which enhance, extend, and repurpose RF systems and waveforms used in space and space-based communications. Projects can include but are not limited to: 1.

demonstrating how telemetry, tracking, and command (TT&C) or other messaging protocols can be used to command large constellations or grouping of space vehicles simultaneously, to include those under high delta-V maneuvers, 2. demonstrating how RF waveforms can be repurposed or exploited for non-traditional use, and 3. improving software-based transmission systems.

2.1.8 Objective 1h: Enable payload hosting

Technology projects can include but are not limited to: 1. hosting various space-to-space communications payloads on RF or optical communications terminal cross-linked host vehicles, and 2. reduced times/costs/complexity for payload integration and launch.

2.2 Focus Area 2: Space Networking

2.2.1 Objective 2a: Enable a high-rate mesh backbone

Projects can include but are not limited to: 1. technologies which enable extremely fast data transfer and minimize latency across networks, 2. optimizing routing and scheduling algorithms,

3. network topologies to facilitate seamless expansion and adaptation to changing network conditions (contested and dynamic environments), counter interference, and ensure reliable data transport in all environments.

2.2.2 Objective 2b: Enable seamless multi-level security (MLS) operations in contested environments Government interest centers on developing MLS systems which are inherently secure, resist attacks, and capable of maintaining operations even when under threat. This includes cross-domain solutions enabling secure information sharing across different security domains and between various "communities of interest" within a multi-level environment, and innovative security architectures for MLS systems. Technology projects can also explore formal methods for robust access control, data separation, and threat detection mechanisms within the architecture.

2.2.3 Objective 2c: Enable cyber defense

Technology projects can include but are not limited to: 1. enhancing cybersecurity posture and resilience, 2. leveraging AI for threat detection, analysis and response, 3. techniques for development and deployment of secure and resilient software, 4. understanding and limiting system exploitability by reducing attack surfaces and responding to emerging vulnerabilities, 5.

technologies and techniques for automated cyber operations, and 6. how use of zero trust architectures and secure supply chains can be applied to reduce risk.

2.2.4 Objective 2d: Enable an enterprise hybrid architecture

The Government is seeking to create scalable space-to-space communications enclaves. The enclaves will enable disparate systems to connect, exchange and process data from and through space. Projects can include but are not limited to: 1. demonstrating how hybrid architectures can be centrally deployed and managed through commercial-off-the-shelf (COTS) or other proven systems, and 2. employment and extension of commercial standards to rapidly connect and operate hybrid space communications architectures, to include delay multiple communication terminal, link and payload types.

3 BAA Structure

3.1 Nomenclature

Calls under this BAA will be numbered as follows:

• Year #1: 1.1, 1.2, 1.3, etc.

• Year #2: 2.1, 2.2, 2.3, etc.

• Year #3: 3.1, 3.2, 3.3, etc.

• Year #4: 4.1, 4.2, 4.3, etc.

• Year #5: 5.1, 5.2, 5.3, etc.

The first number of the call signifies the year number of the five (5) year BAA. The second number delineates the call number within the year.

3.2 Approach

The Government maintains the right to request a targeted data call which will be published via SAM.GOV at any time. All companies will be permitted to respond to the call, regardless of any previous submissions.

Please contact the Contracting Officer for submission of any potentially SENSITIVE or CLASSIFIED MATERIAL. They will provide an appropriate secure email address at that time.

3.2.1 Option 1: Two-Phase Approach

The BAA process will generally consist of two phases: 1. a white paper phase, and 2. a full proposal phase. Under the two-phased approach option, submission and governmental evaluation of white papers is required before invited offerors can submit a full proposal. The white paper phase will be utilized to screen the proposed technical approach (in advance of full proposal invitations) which helps to streamline the down-select process and strike a fair balance between an offeror’s bid and proposal resources and the Government’s evaluation requirements. Offerors submitting white papers may be invited to submit a full technical and cost proposal of their white paper submission; however, any such invitation is in no way an obligation on the part of the Government to award a contract. Decisions regarding the invitation to submit a full proposal will be based on Government evaluation as described in Section 5.14. An offeror that does NOT submit a timely and compliant White Paper is NOT eligible (and thus cannot be invited) to submit a Full Proposal for consideration for an award.

Once submissions, both white papers and full proposals, are evaluated, responses to Offerors will be provided via email notification from the CO as stated herein.

3.2.1.1 Phase 1: White Papers

Phase 1 of the selection process begins with a targeted data call announcement with a request for submission of white papers. Offerors submitting white papers may not be invited to submit a full proposal for any of the following four (4) reasons (not inclusive): 1. Solution not responsive to Government interests, 2. Solution has high schedule and/or cost risk or is unaffordable, 3.

Solution is insufficiently mature for Government development needs, and/or 4. Solution has been tried in the past or is an existing capability.

3.2.1.2 Phase 2: Full Proposals

Phase 2 of the selection process begins when the CO requests selected Offeror/s submit a full technical and cost proposal. An Offeror can be considered for contract award only upon preparation and submission of a fully compliant Phase 2 proposal based on the Government’s request for full proposal. All full proposals will be evaluated in accordance with the evaluation criteria identified in Section 5.14.

The Government may select one, more than one, part, or none of the Offeror’s full proposal for award. If no proposals are deemed acceptable, the Government reserves the right to make no awards. Additionally, the Government reserves the right to accept a full proposal for award consideration in its entirety or may select portions of a full proposal for award consideration and funding. The Government may also recommend revising the technical approach, reshaping and/or re-scoping the effort, including phases, blocks, and shorter periods of performance with the potential for options, if appropriate, to quickly substantiate proof-of-concept or assess the validity or feasibility of the effort for greater potential use. In these cases, revised contract scope, schedule, and funding details will be established during negotiations between the Government and the Offeror.

It is the policy of SSC/SZK to treat all proposals submitted under this BAA as sensitive competitive information and to disclose their contents only for the purposes of evaluation.

3.2.1.3 Notional Timeline – Two-Phase Approach

Table 1 Notional Timeline

Event Calendar Days

BAA Call Released 0

White Papers Due +20

Government Request for Full Proposals +30

Full Proposal Due Date +60

Proposal Evaluation/Negotiations Completed +80

Contract(s) Awarded +90

3.2.2 Option 2: One-Phase Approach

The Government has the option with each targeted BAA call under this basic BAA to skip the white paper phase and go straight to request for proposal (RFP) if warranted and/or necessitated.

The approach will be clearly articulated with each targeted BAA call. The Offeror will need to pay special attention to the instructions and due dates of each call.

3.2.2.1 Phase 1: Full Proposals

Phase 1 of the selection process begins when the CO posts a targeted BAA call to Industry to submit full technical and cost proposals. An Offeror can be considered for contract award only upon preparation and submission of a fully compliant Phase 1 proposal based on the Government’s request for full proposal instructions and meeting the submission timeline. All full proposals will be evaluated in accordance with the evaluation criteria identified in Section 5.14.

The Government will then select one, more than one, a portion of, or none of the proposals for award. If no proposals are deemed acceptable, the Government reserves the right to make no awards. Additionally, the Government reserves the right to accept a full proposal for award consideration in its entirety or may select portions of a full proposal for award consideration and funding. The Government may also recommend revising the technical approach, reshaping and/or re-scoping the effort, including phases, blocks, and shorter periods of performance with the potential for options, if appropriate, to quickly substantiate proof-of-concept or assess the validity or feasibility of the effort for greater potential use. In these cases, revised contract scope, schedule, and funding details will be established during negotiations between the Government and the Offeror.

It is the policy of SSC/SZK to treat all proposals submitted under this BAA as sensitive competitive information and to disclose their contents only for the purposes of evaluation.

3.2.2.2 Notional Timeline – One-Phase Approach

One-Phase Approach (from Government BAA Call)

Table 2 Notional Timeline Event Calendar Days

BAA Call Released 0

Full Proposal Due Date +30-60

Proposal Evaluation/Negotiations Completed +60-90

Contract(s) Awarded +90-120

4 Award and Funding Information The Government anticipates that multiple awards will occur stemming from this basic BAA within the stated period of performance (POP). However, the Government may make no awards at its discretion, subject to changing requirements and the availability of funds. The POP for projects, inclusive of options, may be up to 5 years. The Government may also terminate work at any time if it no longer meets the needs of the Government.

4.1 Eligibility Information/Sources

This is an unrestricted solicitation. All responsible sources, as defined at Federal Acquisition Regulation (FAR) 9.104-1, capable of satisfying the Government’s objectives of this solicitation may submit a white paper and/or proposals (if requested) under this announcement. Small businesses, large businesses, nonprofit, and academic institutions are eligible to submit white papers and/or proposals (if requested) and participate in teaming arrangements for submissions with other industry partners. No portion of this announcement will be set aside for small businesses or other socio-economic participation.

All Offerors submitting white papers and full proposals must:

a. Be registered in the System for Award Management (SAM) prior to submission;

b. Provide a valid unique entity identifier in its submissions; and

c. Maintain an active SAM registration with current information at all times during which it has an active Federal award or an application under consideration by any agency; and

d. SAM may be accessed at https://www.sam.gov/content/home University Affiliated Research Centers (UARCs) are eligible to submit proposals under this BAA unless precluded from doing so by their Department of Defense (DOD) UARC contract.

If Federally Funded Research and Development Centers (FFRDCs) or Government entities (Government/National laboratories, military educational institutions, etc.) are interested in one or more of the programs described herein, the organization should contact the CO directly to discuss its area of interest. FFRDCs and Government entities (Government/National laboratories, military educational institutions, etc.) are subject to applicable direct competition limitations and cannot propose to this BAA in any capacity unless they address the conditions stated below.

FFRDCs FFRDCs must: 1. clearly demonstrate the proposed work is not otherwise available from the private sector, 2. provide a letter on letterhead from their sponsoring organization citing the specific authority establishing their eligibility to propose to Government solicitations and compete with industry, and 3. show compliance with the associated FFRDC sponsor agreement and terms and conditions. This information is required for FFRDCs proposing to be primes or subcontractors.

Government Entities Government entities must: 1. clearly demonstrate that the work is not otherwise available from the private sector and 2. provide written documentation citing the specific statutory authority (as well as, where relevant, contractual authority) establishing their ability to propose to Government solicitations. Specific supporting regulatory guidance, together with evidence of agency approval will be required to establish eligibility.

The CO will consider eligibility submissions on a case-by-case basis; however, the burden to prove eligibility for all team members rests solely with the Offeror.

4.2 Cost Sharing/Funds Matching

Cost sharing is not expected under contracts or agreements awarded from this BAA and will not be used as a factor during the merit review of any proposal hereunder; however, the Government may consider voluntary cost sharing if proposed. While cost sharing is not anticipated, there are certain circumstances where it will be beneficial for vendors to propose cost sharing. Cost sharing is encouraged where there is a reasonable probability of a potential commercial application related to the proposed research and development effort. Additional guidance can be found at 2 Code of Federal Regulations (CFR) 200.306 and FAR 35.003.

5 Submissions – General Information and Instructions

5.1 General Information

The Government will consider proposals to be valid for a period of not less than 180 calendar days from the date of delivery.

5.2 General Instructions

a. The Offeror is expected to examine this entire solicitation document. Failure to do so will be at the Offeror’s own risk.

https://www.sam.gov/content/home

b. The Government may make award based on the initial offer of a full proposal it receives, without discussion of such offer. Proposals shall set forth full, accurate, and complete information as required by this solicitation package (including Attachments listed). The penalty for making false statements in proposals is prescribed in 18 United States Code (U.S.C.) 1001.

c. An Offeror submitting restricted data shall mark it as follows in accordance with the FAR 52.215-1, Instructions to Offerors - Competitive Acquisition, which is incorporated by reference. FAR Clause 52.215-1(e) states: “Restriction on disclosure and use of data.

Offerors that include in their proposals data that they do not want disclosed to the public for any purpose, or used by the Government except for evaluation purposes, shall –

1. Mark the cover 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

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 cover page of this proposal.”

d. The Government assumes no liability for disclosure or use of unmarked data and may use or disclose the data for any purpose. Unless restricted, information submitted in response to this request may become subject to disclosure to the public pursuant to the provisions of the Freedom of Information Act (5 U.S.C. 552)

e. This procurement is conducted under the procedures of FAR Subpart 15 and 35. The policies and procedures of FAR Subpart 15.3 do not apply.

f. The cost of preparing submissions 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 a normal bid and proposal indirect cost as specified in FAR 31.205-

18. Do not lock any files submitted as part of the proposal submission. Proposal prices and terms and conditions shall remain valid for 180 days from the submission date.

5.3 Availability of Equipment and Software

All commercial hardware and software proposed in response to this solicitation document shall have been formally announced for general release on or before the closing date of the solicitation. Failure to have equipment or software announced prior to submission of proposal may render the Offeror’s proposal NOT ACCEPTABLE.

All commercial and non-commercial hardware and software proposed in response to this solicitation document shall not have been formally announced as at its end of life or end of technical support by its publisher or licensor. Proposal of commercial or non-commercial hardware and software that is at its end of life may render the Offeror’s proposal NOT

ACCEPTABLE.

5.4 Security Classification of Submissions

Submissions may be submitted electronically, via the appropriate communication channels (NIPR, JWICS, SGN, SIC, etc.), to the Security POC / contracting officer listed below:

Contracting Officer: Alternate Contracting Officer:

Mr. Robert Chernoff Capt Tobias Richards NIPR: robert.chernoff@spaceforce.mil NIPR: tobias.richards.1@spaceforce.mil Security POC:

Mr. Christopher Colon NIPR: christopher.colon.4@spaceforce.mil

Submissions shall reference the above BAA number in the subject/title of the response.

Submissions shall be either PDF files or Microsoft (MS) Word Documents. This announcement is effective for five years from date of release. Submissions may be delivered at any time during this period; however, specific BAA Calls will have associated deliverable due dates and times.

The SSC/SZ acknowledges that funding constraints may severely limit contract activities but anticipates the ability to execute a limited number of projects through this timeframe.

5.5 Contract Type

A Cost Plus Fixed Fee (CPFF), Cost Reimbursable (CR), and/or Firm Fixed Price (FFP) type contract, is planned to be awarded under this BAA. Offerors with adequate accounting systems (as identified in FAR 16.301-3) shall propose CPFF contracts.

If an Offeror’s proposal enhances work being performed under other DOD projects, the Offeror must clearly identify the point of departure, what existing work will be brought forward, and what new work will be performed under this BAA.

5.6 General Award Information

The Government intends to make multiple awards resulting from this overarching announcement and reserves the right to select for award one, multiple, a portion thereof, or none of the proposals received. The award(s) will be made based on the proposal that is determined to be most advantageous to the Government with appropriate consideration given to the evaluation factors found in Section 5.14 and the availability of funding. Award may not necessarily be made to the proposal offering the lowest cost/price or receiving the highest evaluated rating. The Government reserves the rights to make an award without discussions, conduct discussions if determined to be necessary, and remove Offeror from award consideration should the parties fail to reach agreement on award terms within reasonable time or the Offeror fails to provide requested additional information in a timely manner.

5.7 Notifications

5.7.1 White Papers

All Offerors submitting a white paper in response to this BAA will receive an email message acknowledging Government receipt. If you do not receive a receipt email, your white paper may not have been received. White papers received before the due date will be accepted, but late mailto:robert.chernoff@spaceforce.mil responses may not be accepted, see Section 5.10.2. Upon completion of the Government evaluation of white papers, an e-mail will inform the Offeror that 1) its white paper was selected for invitation to submit a full proposal or 2) that its white paper was not selected and the reason(s) for the non-selection.

5.7.2 Full Proposals

Offerors invited to submit full proposals will receive an email including a request for proposal instruction letter from the Contracting Officer (CO).

5.7.3 Debriefings

White paper evaluation shall not entitle the Offeror to a debriefing as no award can result from a white paper. However, for full proposals, the procedures in FAR 35.008(d) will be followed. Per FAR 15.505, Offerors may request a pre-award debriefing by submitting a written request to the CO within 3 days after receipt of the notice of exclusion from the competition. See FAR 15.505 for more details.

5.8 Use of Non-Government Advisors

The Government intends to use Government personnel for the white paper review and evaluation of proposals. The Government reserves the right to use FFRDC, Systems Engineering and Integration (SE&I), Systems Engineering and Technical Assistance (SETA), or SSC Acquisition and Financial Support (SAFS) contractors who support SSC to provide technical and acquisition advisory support for evaluations of white papers and proposals. The current list of organizations includes: Aerospace, Massachusetts Institute of Technology (MIT) Lincoln Laboratory, MITRE, the System Engineering and Integration (SE&I) contractor Science Applications International (SAIC) and other contractors (e.g., Advanced Concepts and Technology, ARK GSI, Booz Allen Hamilton, KBR, SAVI, SES, Stellar Solutions, etc.) the SSC Acquisition and Financial Support (SAFS) contractor (Tecolote Research) and security support contractor ManTech International.

The list also includes subcontractors to any of these listed organizations that are actively supporting SSC/SZ through these organizations. If those contractors change over the life of the BAA, the Government will advise in writing.

The evaluators and support personnel will be bound by appropriate Non-Disclosure Agreements (NDA) to protect proprietary and sensitive information. Additional NDAs will not be required;

instead, a response to this BAA will be considered an implicit acknowledgement and acceptance of the fact that non-Government advisors will be assisting the Government in this process.

Should the Offeror have any objections to specific companies and/or personnel from participating in the evaluation of proposals, written notification shall be provided to the Contracting Officer within ten (10) calendar days prior to the Offeror’s submission of proposals or concept papers. If there is an objection, the specific reason(s) for the objection(s) shall be stated in the written notification, and the specific support contractor of concern shall be identified.

Additionally, the companies providing SE&I, SETA, SAFS, or other technical/acquisition support services to SSC are prohibited from submitting White Papers and proposals in response to this BAA. While these companies may not have an actual conflict with regard to this BAA activity, companies interested in competing for this effort may receive or be inadvertently exposed to information during performance of their contracts that may provide an unfair advantage in the White Paper review process. Further, additional conflicts of interest may arise if the SSC/SZ decides to transition capabilities developed under the BAA activities into operations.

If an Offeror suspects or is aware of a potential Organizational Conflict of Interest (OCI) or the appearance thereof they shall document the OCI in the concept paper and proposal. If a potential OCI or appearance thereof exists, the offeror shall submit the mitigation plan in place or to be put in place upon award with the concept paper and proposal. Awardees shall mitigate OCIs and shall be in compliance with FAR 9.5 – Organizational and Consultant Conflicts of Interest.

The Government understands that information provided in response to this BAA is presented in confidence and may contain trade secrets, commercial or financial information, and it agrees to protect such information from unauthorized disclosure to the maximum extent permitted or required by:

a. 18 USC 1905 (Trade Secrets Act);

b. 18 USC 1831 et seq. (Economic Espionage Act);

c. 5 USC 552(b)(4) (Freedom of Information Act);

d. Executive Order 12600 (Pre-disclosure Notification Procedures for Confidential

Commercial Information); and

e. Any other statute, regulation, or requirement applicable to Government employees.

5.9 Submission Instructions

5.9.1 Delivery

Offerors shall submit their white papers and, if requested, proposals electronically to the CO.

Only the CO is legally authorized to bind the Government. Offerors are to ensure white papers and/or proposals are received by the Government before the stated submission date to be included in the evaluation. All contractual and technical questions regarding this announcement must be directed to the following points of contact:

Contracting Officer: Alternate Contracting Officer:

Mr. Robert Chernoff Capt Tobias Richards NIPR: robert.chernoff@spaceforce.mil NIPR: tobias.richards.1@spaceforce.mil Technical POC:

Maj Justin Mayfield Email: justin.mayfield.7@spaceforce.mil

5.9.2 Late Submissions

Offerors are responsible for submitting white papers and full proposals so that they are received by the Government no later than the date and time specified. Offerors are encouraged to submit early to avoid potential delays encountered in the course of the submission. All submissions shall be fully submitted before the due date and time to be considered. Late proposals will only be accepted if they comply with FAR 52.215-1(c)(3).

5.10 Facility Clearance

Offerors must be able to certify that they have an appropriate facility clearance to meet the security requirements of the work proposed, and key personnel must be certified as holding an appropriate security clearance. The security clearance level required for these efforts is up to Top mailto:robert.chernoff@spaceforce.mil

Secret/Sensitive Compartmented Information (SCI)/Special Access Required (SAR). Facility Clearance Level will be documented in a DOD Contract Security Classification Specification

(DD254).

5.11 Commitment to Small Business

SSC is strongly committed to providing meaningful subcontracting opportunities for small businesses, small-disadvantaged businesses (SDB), woman-owned small businesses (WOSB), Historically Underutilized Business Zone (HUBZone) small businesses, veteran-owned small businesses, service-disabled veteran-owned small businesses (SDVOSB), historically black colleges and universities, and minority institutions through its awards. For proposed awards that exceed $750,000 to other than small businesses, the Offeror is required to submit a Subcontracting Plan in accordance with FAR 52.219-9. Subcontracting Plans shall be compliant with FAR Subpart 19.7.

Department of Defense Small Business Program Goals are outlined in the below table for reference. Though not mandatory goals for a subcontracting plan, they provide reference for general expectations for subcontracting plans.

Table 4 Subcontracting Goals Subcontracting Goals FY25

Small Business 30%

HUBZone 3%

SDVOSB 5%

SDB 5%

WOSB 5%

5.12 White Paper Instructions

The white paper shall include a discussion of the nature and scope of the Offeror’s proposed technical approach. The Government will review the white papers in accordance with the white paper technical evaluation criteria, set forth in Section 5.14 below. Those Offerors submitting white papers evaluated as having sufficient technical merit and for which funding is available will be asked to submit a full technical and cost proposal.

Those Offerors not invited to submit a full technical and cost proposal will be notified. Any Offeror submitting a full 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 or any other award; however, it may be an allowable expense to the normal bid and proposal indirect cost as specified in FAR 31.205-18.]

a. White Paper Structure A complete white paper shall be limited to seven (7) pages total and consist of three Sections: 1) Cover Page (1 page), 2) Technical Approach (4 pages), and 3) Business Approach (2 pages). The white paper text shall be in PDF format. Text shall be single-spaced (with double-space between paragraphs), on 8½ x 11 inch paper, with one-inch margins all around. Font size shall be of minimum 12-point font.

i. Section 1 – Cover Page The Cover Page shall be one (1) page in length and include: (1) the white paper title with BAA number; (2) company name, website, Federal Tax ID, Commercial and Government Entity (CAGE) Code, Unique Entity Identifier (UEI) and mailing address; (3) business size (e.g., large business, small business) (NAICS Code: 541 – Professional, Scientific, and Technical Services / 541715 – Research and Development in the Physical, Engineering, and Life Sciences (except Biotechnology)); (4) technical and contracts points of contact (including email address, telephone number, and facsimile number); (5) date; and (6) duration of effort;

(7) list of proposed focus area(s) and objective(s) coming from the targeted call; and (8) estimated cost of the BAA effort.

ii. Section 2 – Technical Approach The text contained in Section 2 of the white paper shall describe your technical approach inclusive of the following:

1. Key assumptions,

2. Relevance to one or more BAA focus areas and objectives coming from the targeted call,

3. Summary schedule graphic, and

4. Extent that the approach enhances or accelerates development.

The main text of the white paper, contained in Section 2, is limited to four (4) pages in length, exclusive of cover page and the Business Approach.

iii. Section 3 – Business Approach The text contained in Section 3 of the white paper shall describe your Business Approach. It shall be no more than two (2) pages in length and inclusive of the following:

1. Anticipated POP,

2. Contract type (CPFF, Cost Reimbursable, or FFP) and rationale for proposed contract type,

3. Rough Order of Magnitude (ROM) - No certified cost or pricing data is required

• Breakout by Offeror selected deliverable(s) as detailed in the targeted call

• Provide any additional ROM details as stated in the targeted call

• Time-phase costs by Government Fiscal Year (GFY)

• Discuss any cost drivers, assumptions, and unknowns; and

• GFE must be identified but not priced.

4. Teaming/Partnership Arrangements - highlight small business teaming if applicable

5. Required Security Posture - Facility Clearance (FCL) and DD254 requirements

5.13 Full Proposal Instructions

Each offer shall be provided to the Government in three parts. The Offeror shall submit each part separately. The submission shall contain the following:

• Part I: Contract Administrative Proposal

• Part II: Contract Cost/Price Proposal

• Part III: Technical Proposal

Unless otherwise specified, a single electronic page in 8.5” x 11” format will be counted as one page where page limitations apply. All electronic files shall be in MS Word, PowerPoint, PDF, or Excel formats.

Electronic proposal pages (except for Excel and PowerPoint) must maintain one-inch margins.

Excel files must maintain margins of no less than 0.7”, and PowerPoint files must maintain margins of no less than 0.5”. Electronic proposal pages must maintain 12-point Times New Roman font and be single spaced, except for charts/graphics/tables.

Charts/Graphics/Tables must maintain a minimum of ten-point Times New Roman font, including in the Part II slides. Charts/Graphics/Tables embedded in the proposal will count toward page limitations. Headers and footers may be of a font larger than 12 point but shall not be smaller than ten-point font.

Items such as a Cover Page, Table of Contents, Cover Letter, List of Figures, and Acronym Lists are excluded from the page counts below. PDF files will be allowed for executed documents such as Letters of Commitment.

Any pages submitted beyond the page limitations will be removed and not evaluated.

Table 2 Overall Proposal Contents Part Section Page Limit

I Contract Administrative Proposal

a. Cover Letter 2

b. OCI Statement (Attachment A) No Limit

c. Certifications and Representations No Limit

II Contract Cost/Price Proposal

a. Cost/Price Excel File No Limit

b. Cost/Price Narrative No Limit

c. Subcontractor Supporting Documentation No Limit

d. Assumptions No Limit

e. Rates No Limit

f. Business Systems No Limit

III Technical Proposal

a. Technical Approach 10

b. Technical Assumptions 1

c. Relevance to Focus Areas and Objectives (coming from the targeted call) 1

d. Summary Schedule Graphic and Extent that the Approach Enhances or Accelerates Development

Part I - Contract Administrative Part I shall contain the following sections:

a. Cover Letter Cover Letter shall include the following:

Company Name, Data Universal Numbering System (DUNS) # and CAGE Code as reflected in System for Award Management, https://www.sam.gov.

b. OCI Statement (Attachment A):

The Offeror and each subcontractor, consultant, teaming partners, and individuals involved in proposal development shall complete and sign an OCI Statement (Attachment A). An Offeror https://www.sam.gov/ who has refused to disclose the information or make the certification required by this BAA concerning an actual or potential OCI shall be disqualified from consideration for award.

Each signed OCI statement will be excluded from the page count. The OCI Statement shall disclose all projects that meet the specified criteria in this BAA. The Offeror should be aware that performance under this contract may preclude the Offeror from competing for any future requirement that incorporates, involves, or relates to any work performed by the Offeror under the awarded contract.

The Offeror shall provide a copy of any existing mitigation plan(s) from the relevant awarded contract(s) identified. If an existing mitigation plan does not exist, and an Offeror with an actual or potential OCI believes the conflict can be avoided, neutralized, or mitigated, the Offeror shall submit a new mitigation plan to the Government for review.

In addition to the mitigation plan, the CO may require further information from the contractor. The CO will use all information submitted by the contractor, and any other relevant information known to SSC/SZ, to determine whether an award to the contractor may take place, and whether the mitigation plan adequately avoids, neutralizes, or mitigates the OCI. If any such conflict of interest is found to exist, the CO may determine that the conflict cannot be avoided, neutralized, mitigated, or otherwise resolved to the satisfaction of the Government, and the contractor may be found ineligible for award. Alternatively, the CO may determine that it is otherwise in the best interest of the U.S. to contract with the contractor and include the appropriate provisions to avoid, neutralize, mitigate, or waive such conflict in the contract awarded.

c. Certifications and Representations

In accordance with FAR 4.1102 and 4.1201, offerors submitting a proposal must complete electronic annual representations and certifications at https://www.sam.gov/. Additionally, resultant contracts may require supplementary SCP-specific representations and certifications.

The Offeror shall also provide a copy (screenshot is acceptable) of its assessment in the Supplier Performance Risk System (SPRS) (https://www.sprs.csd.disa.mil/)

Part II - Contract Cost/Price Proposal Overall Cost/Price Guidance For Cost Reimbursement type contracts, audits may be performed by Defense Contract Audit Agency (DCAA) on the Offeror and all subcontracts. Written Price Proposals shall meet the DCAA audit submittal requirements. The Offeror shall fully support all proposed prices. The Offeror’s proposal is presumed to represent the Offeror’s best efforts in response to the solicitation. Any inconsistency, whether real or apparent, between promised performance and cost/price, shall be explained in the proposal.

The Offeror shall provide adequate information, which will allow the Government to perform a Cost Realism analysis. Pursuant to FAR 15.404-1(d)(1), Cost Realism analysis is defined as:

“…the process of independently reviewing and evaluating specific elements of each Offeror’s proposed cost estimate to determine whether the estimated proposed cost elements are realistic for the work to be performed; reflect a clear understanding of the requirements; and are consistent with the unique methods of performance and materials described in the Offeror’s technical proposal.”

As indicated in Attachment B under FAR Clause 52.215-20, a description of the data required to be submitted with the Offeror’s proposal in order to facilitate the Cost Realism analysis is provided below.

Written Cost/Price Proposals shall be submitted electronically via the method indicated in the solicitation. The Offeror shall submit all proposed costs/prices using MS Excel software utilizing the formats without cells locked and including all formulas. The Offeror shall include adequate information, which will allow the Government to perform the required Cost Realism analysis.

The Offeror shall not include any cost/price data in Parts I and III of the proposal.

Part II shall contain the following sections:

a. Cost/Price Sheet (Attachment B)

b. Cost/Price Narrative

1. The Offeror shall provide a detailed cost narrative, which explains the processes and methodologies used to develop its written Cost/Price Proposal. This includes, but is not limited to, the estimating methodology used by the Offeror to estimate direct labor and subcontractor labor, explanation of the application of indirect rates, planning assumptions used in the development of the cost estimate, etc.

2. The Offeror shall also include a basis of cost element, weightings, and explanations to those in the solicitation.

3. The Offeror shall specifically indicate in its narrative any applicable Uncompensated Overtime Policy and how such policy affects the hourly direct labor rates and Full- Time Equivalent (FTE) hours being proposed during any contract year.

c. Subcontractor Supporting Documentation

1. The Offeror shall provide supporting cost/price documentation for all proposed subcontractors, including the total value of the proposed subcontract, the proposed type of subcontract, the rationale and/or justification for this type of subcontract type, and how fee will be determined and paid.