SDN-B MOC CSO Post_30 Apr 26.pdf

COMMERCIAL SOLUTIONS OPENING (CSO)

(Solicitation FA8819-26-R-B010) for Space Data Network Backbone (SDN-B) Mission Operations Center (MOC) in support of Space Systems Command (SSC)

System Delta 89 (SYD 89) Spectrum Warfare Division

CSO Summary

Title SDN-B MOC Posted Date 30 April 2026 North American Industry Classification System (NAICS)

541715

CSO Type Closed / 3-step Step 1 Open Period Closes 12:00pm Pacific Daylight Time (PDT) 18 May 2026

(late submissions will not be accepted; Offerors are responsible for verifying receipt)

Steps 2 and 3 By invitation only; the Government will not accept unsolicited proposals

Contract Vehicle Single Award Indefinite Delivery, Indefinite Quantity (IDIQ) or Other Transaction Agreement (OTA)

Contract Type Firm Fixed Price (FFP); all supplies or services procured via this CSO will be treated as commercial

Anticipated Period of Performance (POP)

60 months

Security Requirements 1. Restricted to domestic Unite States (US) based companies and US based subsidiaries

2. Must have an active Sensitive Compartmented Information (SCI) Facility Clearance (FCL) with cleared personnel

This posting of the CSO does not commit the Government to contract for any supply or service.

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 CSO shall be submitted in writing to the POCs listed below.

Contracting Officers (COs):

Ms. Melanie Gipson

SSC/SZK

483 N. Aviation Blvd. A-8 Telephone: (310) 653-9220 Email: melanie.gipson@spaceforce.mil Capt Tobias Richards

SSC/SZK

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

Security POCs:

Mr. Steven Mafla

SSC/SZ

483 N. Aviation Blvd. A-8 Telephone: (310) 653-9741 Email: steven.mafla.ctr@spaceforce.mil

Ms. Rebecca Williams

SSC/SZ

483 N. Aviation Blvd. A-8 Telephone: (310) 653-9012 Email: rebecca.williams.4.ctr@spaceforce.mil

Technical POC:

Maj Anthony Gentry

SSC/SZWM

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

Table of Contents 1 Background 5

1.1 Space Data Network Backbone (SDN-B) Mission Operations Center (MOC) Scope 5

1.2 Commercial Viability 5

2 Problem Statement, Operational Challenges, and Desired Outcome 6 3 General Information 6

3.1 Approach 6

3.2 Notional Timeline 8

4 Award Information 8

4.1 Eligibility Information/Sources 8

5 Submissions – Information and Instructions 9

5.1 General Information 9

5.2 General Instructions 9

5.3 Availability of Equipment and Software 10

5.4 Contract Type 10

5.4.1 Contract Line Item Number (CLIN) Structure 10

5.5 Notifications 11

5.5.1 Written Solution Briefs (white papers) 11

5.5.2 Full Proposal Invitation 11

5.5.3 Debriefings 11

5.6 Use of Non-Government Advisors 11

5.7 Submission Instructions 12

5.7.1 Delivery 12

5.7.2 Late Submissions 13

5.8 Facility Clearance 13

5.9 Commitment to Small Business 13

5.10 Step 1: Solution Brief Instructions 14

5.10.1 Format 14

5.10.2 Cover Page 14

5.10.3 Narrative 14

5.11 Step 2: Pitch Day Instructions (by invitation only) 16

5.11.1 Format 16

5.11.2 Content 16

5.11.3 Time Requirements 16

5.11.4 Offeror Attendees 17

5.11.5 Pitch Day Security Classification 17

5.12 Step 3: Full Proposal (by invitation only) 17

6 Evaluation and Selection Information 17

6.1 Scientific Peer Review 17

6.2 Step 1 and 2 Evaluation Factors 17

6.2.1 Factor #1: Technical Approach 18

6.2.2 Factor #2: Schedule 18

6.2.3 Factor #3: Overall Value 18

6.2.4 Factor #4: Offeror Capabilities and Experience 18

6.3 Step 3 Evaluation Factors 18

7 Data Rights and Proprietary Data 18

7.1 Procurement of Commercial Items on Behalf of the Government 18

7.2 Government Purpose Rights (GPR) 18

7.3 Government Rights Prior to Contract Award 18

7.4 Pre-Proposal Communication between Prospective Offerors and Government Representatives 19

8 Request for Bidders Library and CUI Submission Instructions 19

8.1 Contractor Requirements for CUI Access 19

8.1.1 CUI Solution Brief / Pitch Day Submission Instructions 20

1 Background The Government desires a MOC design and implementation approach that will seamlessly integrate the entire SDN-B architecture with modularity for future expansion: commercial proliferated low Earth orbit (pLEO) providers, government/commercial transport, ground elements, and Space Exchange Points (SEPs). The SDN-B MOC will be the centralized hub that “brokers” user services, mission plans, and resources. It will deliver enterprise-wide situational awareness and a common operational picture of all SDN ground and space assets.

The MOC requires a hybrid deployment, utilizing both an on-premises and cloud-based hardware and software to provision, orchestrate, control, and manage the network transport services. It will serve as the primary interface for processing user service requests and ensures end-to-end service performance by monitoring the health, status, and performance of all SDN network elements. The MOC will operate as a Government-Owned, Contractor-Operated (GOCO) facility, designed with a Modular Open Systems Approach (MOSA) to ensure future adaptability and integration.

1.1 Space Data Network Backbone (SDN-B) Mission Operations Center (MOC) Scope The MOC will be an enterprise system responsible for the unified management of the SDN Backbone. The MOC scope includes the following:

• Commercial procurement with modification development for system specific characteristics,

• lifecycle management,

• technology refreshes,

• pLEO provider services management,

• network performance monitoring,

• orchestration of space transport network connectivity,

• user onboarding,

• information assurance processing, and

• sustainment and other related tasks.

1.2 Commercial Viability

The Government is seeking innovative commercial solutions that may be adapted for Government use. This CSO is limited to commercial products or services that are considered innovative, defined as: 1) any new technology, process, or method, including research and development; or 2) any new application of an existing technology, process, or method.

This includes, but is not limited to, the application of existing commercial cloud management tools for MOC service orchestration, the adaptation of commercial Artificial Intelligence (AI)/Machine Learning (ML) analytics for network performance monitoring, or the use of commercial data visualization platforms for the common operational picture.

Proposals for a completely bespoke Government-unique MOC built from the ground up without a clear foundation from an existing or emerging commercial capability will be considered out of scope.

2 Problem Statement, Operational Challenges, and Desired Outcome Problem: Absence of a unified enterprise system for the management, service orchestration, and situational awareness of the multi-vendor and multi-band SDN architecture across multiple concurrent missions.

This overarching problem manifests in several critical operational challenges:

• Systems of Systems Engineering and Integration: Enterprise interoperability and operational effectiveness, onboarding/integrating new systems and users, and unified technical and architectural governance.

• Dynamic Management of a Multi-Mission/Vendor Enterprise: Seamlessly orchestrate services across the diverse and growing ecosystem of Government systems and commercial satellite providers that make up the SDN backbone each with unique management systems.

• Prioritization: Enforce US Space Force (USSF) mission priorities across the entire enterprise in real-time

• Unified Situational Awareness: Achieve a single, end-to-end operational picture for health, status, and performance

• Manual Operations: Key functions such as service provisioning, network monitoring, and fault management are manually intensive.

• Increased Operator Workload and Decision Latency: The manual correlation of data from different systems places a high cognitive load on operators.

The MOC is being acquired to solve this problem and operational challenges by 1. providing a platform for the enterprise management of the SDN Backbone, 2. increasing resilience, 3.

reducing operator workload, and 4. ensuring data delivery to the warfighter.

Desired Outcome: Encompasses a solution that can fulfill all requirements and objectives presented in the MOC Statement of Work (SOW) and Technical Requirements Document (TRD).

3 General Information

3.1 Approach

Under the CSO, the Space Force may competitively award proposals received in response to a general solicitation, like a broad agency announcement (BAA), to acquire innovative commercial items, products, technologies, and services, based on a review of proposals by scientific, technological, or other subject-matter expert peers within the Space Force. For the SDN-B MOC effort, the Government will utilize either Revolutionary Federal Acquisition Regulation (FAR) Overhaul (RFO) Subpart 16.5 for Indefinite-Delivery Contracts or 10 US Code (USC) 2371b Other Transaction Authority (OTA). Under this CSO, all items, products, technologies, and services shall be treated as commercial items and only a single contract award/agreement will be made; items, products, technologies and services do not have to be “commercially available” to be submitted in response to this solicitation. If the solution meets the requirements of the regulation, the solution is treated as commercial whereby the CO will utilize commercial procedures to develop and execute the resultant award/agreement.

The Space Force intends to obtain “innovative” solutions or potential new capabilities that fulfill requirements, close capability gaps, or provide potential technology advancements. Solutions may include existing technologies or procedures that are not currently in use by units at various locations that would enhance or streamline their mission capabilities.

“Innovative” is defined as: (1) Any technology, process, or method, including research and development, that is new as of the date of submission of a proposal; or (2) Any application that is new as of the date of submission of a proposal of a technology, process, or method existing as of such date.

"Other Transaction for Prototype Projects” refers to this type of OTA. This type of OTA is authorized by 10 USC 2371b for prototype projects directly relevant to enhancing the mission effectiveness of military personnel and the supporting platforms, systems, components, or materials proposed to be acquired or developed by the DOW, or for the improvement of platforms, systems, components, or materials in use by the armed forces. This type of OTA is treated by DOW as an acquisition instrument, commonly referred to as an "other transaction" for a prototype project or a Section 2371b "other transaction".

“Prototype” can generally be described as a physical or virtual model used to evaluate the technical or manufacturing feasibility or military utility.

“Nontraditional Defense Contractor” means as the term is defined in section 2302(9) of title 10 USC. With respect to applicable authority, means 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 Department of War (DOW) for the procurement or transaction, any contract or subcontract for the DOW that is subject to full coverage under the cost accounting standards prescribed pursuant to section 1502 of title 41 and the regulations implementing such section. This includes all small business concerns under the criteria and size standards in Title 13, Code of Federal Regulations (CFR), part 121.

The Government will utilize a 3-step approach for the SDN-B MOC CSO.

• Step 1 – Written Solutions Brief (white papers) (open to all that meet security requirements)

• Step 2 – Oral Presentation / Pitch / Demos (invitation only)

• Step 3 – Request for Commercial Solution Proposal (CSP) (invitation only) Submission and Governmental evaluation of written solution briefs (white papers) is required before invited Offerors can proceed to step 2 or 3. The written solution brief phase will be utilized to screen the proposed technical approach (in advance of oral presentations and 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 written solution briefs (white papers) may be invited to an oral presentation / pitch day and subsequently invited to submit a full technical and cost proposal of their solution brief 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 6. The Government reserves the right to forgo Step 2 and go directly to Step 3. The Government may decide some Offerors require a Step 2 to be considered for Step 3, while other Offerors do not. An Offeror that does NOT submit a timely written solution brief is NOT eligible (and thus cannot be invited) to move forward. Once submissions are evaluated, responses to Offerors will be provided via email notification from the CO as stated herein.

3.2 Notional Timeline

Table 1 Notional Timeline

Event Calendar Days

CSO Posted 0

Step 1: Written Solution Briefs Due CSO Post +18

Government Invites to Step 2 Sent CSO Post +25

Step 2: Oral Presentations / Pitch Days CSO Post +29

Government Invites to Step 3 Sent / Request for Proposal (RFP) Issued CSO Post +38

Proposals Due CSO Post +68

*Timeline is notional and subject to change 4 Award Information The Government intends to make a single award from this CSO. However, the Government may make no awards at its discretion, subject to changing requirements and the availability of funds.

The period of performance (POP) for this project, 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 RFO 9.104-1 and herein, capable of satisfying the Government’s objectives of this solicitation may submit a written solution brief and/or an oral presentation or proposal (if requested) under this announcement. The resulting contract/agreement award will not be a small business set aside.

All Offerors submitting a written solution brief and/or an oral presentation or proposal (if requested) must:

a. Be registered in the System for Award Management (SAM) prior to submission (SAM may be accessed at https://www.sam.gov/content/home);

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

c. Be listed in SAM.GOV with the NAICS Code: 541 – Professional, Scientific, and Technical Services / 541715 – Research and Development in the Physical, Engineering, and Life Sciences (except Biotechnology);

d. Provide a valid unique entity identifier in its submissions;

e. Have updated required representations and certifications (RFO 52.240-90); and

f. Comply with Defense Revolutionary Federal Acquisition Regulation Supplement (R-

DFARS) 252.240-7997 (current National Institute of Standards and Technology Special https://www.sam.gov/content/home

Publication (NIST SP) 800-171 assessment posted in Supplier Performance Risk System (SPRS), if applicable)

5 Submissions – 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.

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

c. An Offeror submitting restricted data shall mark it as follows in accordance with the RFO 52.215-1, Instructions to Offerors - Competitive Acquisition, which is incorporated by reference. RFO 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 USC 552)

e. This procurement is conducted under the procedures of R-DFARS Subpart 212.70 and RFO Part 35.

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 RFO 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 Contract Type

A FFP type contract is planned to be awarded under this CSO. If an Offeror’s proposal enhances work being performed under other DOW 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 CSO.

5.4.1 Contract Line Item Number (CLIN) Structure

The following table outlines the proposed CLIN structure for the purposes of the CSO. Final CLIN structure to be detailed within the RFP.

Table 2 Notional CLIN Structure

CLIN Title / Description POP Contract Type

Priced and Evaluated

0100 MOC Development:

Software development, internal ICDs, points of presence (PoPs) development and installation, MOC fit-up, contractor logistics support (CLS), transition plan development (see SOW)

ATP

30 Sep 28

FFP Yes

0101 Data and Reports ATP

30 Sep 28

Not Separately Priced (NSP)

N/A

0200 System of System (SoS) Engineering:

Lead integrator role, external ICDs, Model Based System Engineering (MBSE) modeling, architecting SDN-B (see SOW)

ATP

30 Sep 28

FFP Yes

0201 Data and Reports ATP

30 Sep 28

Not Separately Priced (NSP)

N/A

CLIN Title / Description POP Contract Type

Priced and Evaluated

0300 Materials ATP

30 Sep 31

Cost Reimbursable

(CR)

Yes

(Option)

Future Capability Releases (CRs):

Post MVCR / phase IB (see SOW)

01 Oct 28

30 Sep 31

FFP No

(Option)

Demonstration To Be Determined

(TBD)

FFP No

(Option)

Studies TBD FFP Rate is Proposed and

Evaluated

5.5 Notifications

5.5.1 Written Solution Briefs (white papers)

All Offerors submitting a written solution brief in response to this CSO will receive an email message acknowledging Government receipt. If you do not receive a receipt email, your written solution brief may not have been received. It is the Offeror’s responsibility to reach out to the Contracting Officer and verify receipt. Written solution briefs received before the due date will be accepted, but late responses may not be accepted, see section title “Late Submissions”. Upon completion of the Government evaluation of written solution briefs, an e-mail will inform the Offeror that 1) its written solution brief was selected for invitation to Step 2. Oral Presentation / Pitch Day or 2) that its written solution brief was not selected or 3) the Offeror is invited to Step 3.

5.5.2 Full Proposal Invitation

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

5.5.3 Debriefings

Written solution brief / oral presentation (pitch day) evaluation shall not entitle the Offeror to a debriefing as no award can result from either of these steps for this CSO. However, for full proposals to an IDIQ RFP, the procedures in RFO 35.201(b) will be followed.

5.6 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 Federally Funded Research and Development Center (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 SE&I contractor Science Applications International (SAIC) and other contractors (e.g., Advanced Concepts and

Technology, ARK Government Solutions Inc. (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.

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 CSO 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 CO 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 solution briefs, pitches, and proposals in response to this CSO. While these companies may not have an actual conflict with regard to this CSO 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 evaluation process.

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 RFO 9.5 – Organizational and Consultant Conflicts of Interest.

The Government understands that information provided in response to this CSO 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 (EO) 12600 (Pre-disclosure Notification Procedures for Confidential

Commercial Information); and

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

5.7 Submission Instructions

5.7.1 Delivery

Submissions must be submitted electronically via the appropriate communication channels. The Government is ONLY accepting unclassified or CUI material for Step 1 written solution brief.

Offerors shall submit their unclassified written solution brief and, if requested, oral presentation / proposal electronically to the CO and Alternate CO (listed below). Only the CO is legally authorized to bind the Government. Offerors are to ensure solution briefs and/or oral presentations / 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:

Ms. Melanie Gipson Capt Tobias Richards NIPR: melanie.gipson@spaceforce.mil NIPR: tobias.richards.1@spaceforce.mil Technical POC:

Maj Anthony Gentry NIPR: anthony.gentry.1@spaceforce.mil

If the Offeror has a CUI written solution brief and if requested, oral presentation / proposal, see section 8.1.1 below for CUI Submission Instructions.

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

Submissions shall be either portable document format (PDF) files or Microsoft (MS) Word Documents for written solution briefs and full proposals. Oral presentations may be submitted in either PDF files or Microsoft PowerPoint. If a file size is extremely large, this file may have to be submitted in PDF format.

5.7.2 Late Submissions

Offerors are responsible for submitting written solution briefs and/or oral presentations / 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 RFO 52.215-1(c)(3). It is the Offeror’s responsibility to verify receipt of submissions.

5.8 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 Secret/Sensitive Compartmented Information (SCI) Facility Clearance Level will be documented in a DOW Contract Security Classification Specification (DD254).

5.9 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 $900,000 to other than small businesses, the Offeror is required to submit a Subcontracting Plan in accordance with RFO 52.219-9. Subcontracting Plans shall be compliant with RFO Subpart 19.206.

Department of War Small Business Program Goals & Performance are stated on the mailto:tobias.richards.1@spaceforce.mil mailto:anthony.gentry.1@spaceforce.mil following website: https://business.defense.gov/About/Goals-and-Performance/. Though not mandatory goals for a subcontracting plan, they provide reference for general expectations for subcontracting plans.

5.10 Step 1: Solution Brief Instructions

5.10.1 Format

A complete solution brief shall be limited to 15 pages total with a 10-page maximum for the Technical Solution section. The remaining section (Schedule, Cost, and Prior Experience) page counts will be added to the page count of the Technical Solution section to fit within the 15-page limitation. For example, if an offeror chooses to submit a 10-page Technical Solution section, the offeror will then have five (5) pages left for the remaining three (3) sections on Schedule, Cost, and Prior Experience.

The white paper text shall be in Microsoft Word or 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. Pages in excess of the page limitation will not be read or evaluated.

5.10.2 Cover Page

The solution brief shall contain a one (1) page cover sheet containing the following information:

• CSO number

• Solution Brief Title

• Full company name, website, and address

• Commercial and Government Entity (CAGE) Code

• Unique Entity Identifier (UEI)

• Business Size Classification (e.g., large business, small business)

• Current FCL

• Technical and contracts points of contact (including email address and telephone number)

• Overall Estimated Cost The cover sheet will not count against the page limitation.

5.10.3 Narrative

Each Offeror shall describe their plans, referencing the MOC Draft SOW and TRD, to provide an innovative solution according to the table below:

Table 3 Solution Brief Contents Technical Solution (10 page maximum)

• System of Systems (SoS) Integration Describe the planned SoS integration and test approach Demonstrate a thorough understanding of the MOC scope and complexity in relation to the SDN-B, multiple space providers with associated ground architecture, and a dynamic user environment

• Phased Approach to MOC Development

Describe the planned iterative approach leveraging Commercial Off the Shelf (COTS) products to reduce development needs while maximizing capability provided in minimum viable product (MVP), minimum viable capability release (MVCR), and CRs.

(Address non-recurring engineering (NRE) cost and schedule timeline in separate non-technical sections)

• MOC Architecture and Development Describe the design and implementation of the MOC architecture incorporating: modularity, a planned approach to field SDN-B PoPs, hybrid or cloud-based services, COTS, and cybersecurity and multi-level security requirements

• Network Management & Orchestration Describe the approach to manage and monitor: communication resources, SDN network devices, and policies across multiple space and ground system network service providers (include anomaly detection and resolution capabilities)

• Operations Center Describe ability to establish an operations center in a Government provided facility with associated maintenance, staffing, support, training; include on-premises vs. off-premises architecture implementation and cloud solutions for a primary and backup center

• MBSE Modeling Briefly address the utility of MBSE modeling and implementation ideas Schedule Include a schedule narrative, major delivery timelines, and/or major milestones including but not limited to:

• Proposed design review(s)

• MVP (NLT ATP+12 months)

• MVCR (NLT ATP+24 months)

• Future CRs (at least one annually after MVCR)

• Interim Authorization to Test (IATT) and Authority to Operate

(ATO)

• Delineate critical path if known

Cost

• FFP Rough Order of Magnitude (ROM) By program phase and CLIN (where applicable) NRE breakout to include COTS software, licensing, Free and

Open Source Software (FOSS), and development costs Annual CLS ROM

Prior experience • Relevant and recent (5 years) examples of prime contractor experience Relevance regarding MOC technical solution and schedule

• System Integrator experience with defining interfaces and planning and executing system level tests for a system with multiple stakeholders

5.11 Step 2: Pitch Day Instructions (by invitation only)

Offerors may be invited to a pitch day session to expand upon the written solution brief concept/technology/solution.

5.11.1 Format

PowerPoint charts (.ppt) or PDF (can be 4:3 or 16:9 aspect ratio). The Offeror shall deliver presentation slides that will be used for their oral presentation. If Offerors intend to imbed videos in their presentations, Offerors must work with the Technical and Security POCs in advance of submission to ensure file transmission and videos work as intended.

5.11.2 Content

During Step 2 Pitch Day, the Offeror must include the following information:

• Expand upon the technical solution provided in the written solution brief

• Describe or demonstrate how the proposed solution represents an innovative application of commercial technology

• FFP cost details

• Schedule detailing the critical path if known

• Any Intellectual Property (IP) involved in the effort and associated restrictions on the

Government’s use of that IP

• Information requested per the Government’s invitation to Step 2

• Real-time clarification/details on the written solution brief and presentation

5.11.3 Time Requirements

Presentation will flow as follows:

• 60-90-minute Technical Approach presentation (demos are allowed and encouraged)

• 30-60-minute Government only caucus

• 30-minute question-and-answer session The Government will finalize the pitch presentation time limits in the Step 2 invitation. At this time, the Government estimates that Offerors will be given 60-90 minutes and the Government will caucus for 30-60 minutes. The Government will limit interruption/exchanges with the Offeror during the initial presentation. The Government will engage in exchanges with the Offeror during the question-and-answer section to clarify aspects of the pitch. These exchanges are considered part of the oral presentation process and do not obligate the Government to move forward to Step 3.

Slides not briefed, or additional information not otherwise requested that is provided during the oral presentations will not be evaluated. The notes section of PowerPoint charts will not be evaluated.

5.11.4 Offeror Attendees

Up to 8 Offeror representatives may attend and participate in their company’s oral presentation.

5.11.5 Pitch Day Security Classification

The presentations will be held in a Sensitive Compartmented Information Facility (SCIF) near Los Angeles Air Force Base, El Segundo, CA, and may include written and spoken information up to the Top Secret//SCI level. If the Offeror intends to submit a Pitch Day presentation above the CUI level, the Offeror must notify the individuals listed below no later than (NLT) three (3) workdays in advance of the submission date to determine the submission method. Methods of electronic transmission of Top Secret//SCI are limited to Joint Worldwide Intelligence Communications System (JWICS) and Secure Internal Communication (SIC). If a file size is extremely large, this file may have to be submitted in PDF format.

Contracting Officer: Alternate Contracting Officer:

Ms. Melanie Gipson Capt Tobias Richards NIPR: melanie.gipson@spaceforce.mil NIPR: tobias.richards.1@spaceforce.mil

Security POCs:

Mr. Steven Mafla Ms. Rebecca Williams

SSC/SZ SSC/SZ

Email: steven.mafla.ctr@spaceforce.mil Email: rebecca.williams.4.ctr@spaceforce.mil Technical POC:

Maj Anthony Gentry NIPR: anthony.gentry.1@spaceforce.mil

5.12 Step 3: Full Proposal (by invitation only)

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

6 Evaluation and Selection Information Procurement Integrity requirements shall be followed in accordance with 41 USC 423.

6.1 Scientific Peer Review

The selection of Step 1 Solution Briefs and Step 2 Pitches submitted in response to this CSO will be evaluated in accordance with evaluation criteria specified herein through a scientific peer review process, in accordance with RFO 35.2.

6.2 Step 1 and 2 Evaluation Factors

Solution Briefs may be rejected for one or more of the following reasons:

1. Solution not responsive to Government interests,

2. Solution has high schedule and/or cost risk or is unaffordable, and/or

3. Solution is insufficiently mature for Government development needs.

If not rejected, then evaluations will be based on the following criteria in descending order of importance:

mailto:tobias.richards.1@spaceforce.mil mailto:steven.mafla.ctr@spaceforce.mil mailto:anthony.gentry.1@spaceforce.mil

• Factor #1: Technical Approach

• Factor #2: Schedule

• Factor #3: Overall Value

• Factor #4: Offeror Capabilities and Experience

6.2.1 Factor #1: Technical Approach

The Government will evaluate the degree to which the technical approach (as identified in Table 3 Solution Brief Contents, TRD, and SOW) is technically feasible, meets requirements, and has manageable risk.

6.2.2 Factor #2: Schedule

The Government will evaluate the degree to which the approach meets or accelerates Government capability timelines.

6.2.3 Factor #3: Overall Value

The Government will evaluate the degree to which the ROM and schedule alongside technical excellence, innovation, risk, and Offeror experience present the best overall value to the Government.

6.2.4 Factor #4: Offeror Capabilities and Experience

The Government will evaluate the degree to which the Offeror has relevant and recent Prime Contractor and System Integrator experience.

6.3 Step 3 Evaluation Factors

Step 3 evaluation factors will be provided with the request for proposal.

7 Data Rights and Proprietary Data Offerors shall identify technical data developed at private expense that would be used in this effort, as well as ROMs for licensing and Government purpose rights.

7.1 Procurement of Commercial Items on Behalf of the Government

The successful Offeror will be required to act as a procurement agent on behalf of the Government for all COTS software. The US Government must be established as the named Licensee and End User in all End User License Agreements (EULAs).

7.2 Government Purpose Rights (GPR)

The Government seeks GPR in technical data for any newly developed capabilities resulting from this contract.

7.3 Government Rights Prior to Contract Award

The Government (along with selected scientific and engineering expert personnel and support contractor personnel disclosed) will treat written solution briefs the same as bid and proposal information (see R-DFARS 252.227-7991). Written solution briefs, oral presentations, or full proposals containing data that is not to be disclosed to the public for any purpose or used by the Government except for evaluation purposes shall include the following statement on the cover page:

“This document 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 purposes other than evaluation. 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, and disclose this data to the extent provided in the resulting award document. 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 marked "Proprietary" or that contain the legend prescribed by RFO 52.215-1.”

7.4 Pre-Proposal Communication between Prospective Offerors and Government

Representatives Dialogue between prospective Offerors and Government representatives is encouraged.

Technical and contracting questions can be resolved in writing or through open discussions.

Discussions with any of the points of contact shall not constitute a commitment by the Government to subsequently fund or award any proposed effort. Only Contracting Officers are legally authorized to commit the Government.

8 Request for Bidders Library and CUI Submission Instructions For this CSO, there are four (4) DRAFT documents (1. TRD, 2. SOW, 3. Contract Data Requirements List (CDRL), and 4. Compliance Document List (CDL)) available to interested Offerors that meet the security requirements on the CSO title page and plan to submit solution briefs (white papers).

There is an Operations Security (OPSEC) requirement to ensure all recipients of the CUI files meet access criteria in accordance with (IAW) 32 CFR Part 2002, the National Industrial Security Program Operating Manual (NISPOM), and DOW Instruction (DOWI) 5200.48 titled “Controlled Unclassified Information (CUI)” as CUI is not releasable to the public.

To request and obtain the bidders library, please follow the process below. Please allow up to three (3) business days to process your request.

8.1 Contractor Requirements for CUI Access

1. Self-Attestation of Compliance

• Contractors must implement the security requirements in NIST SP 800-171 (110 controls) for protecting CUI in non-federal systems.

• Offerors must submit a self-assessment score in the SPRS, per R-DFARS 252.240-7997.

• If not fully compliant, Offerors must have a System Security Plan (SSP) and a Plan of Action

& Milestones (POA&M).

2. Flow-down Requirements If an Offeror plans to share this CUI with a subcontractor, they must ensure that subcontractor also complies with R-DFARS 252.204-7012 and NIST 800-171.

3. Contractor Verification Prospective Offerors must send an email to both security POCs (listed below) with the subject line “SDN-B MOC CSO Request for Bidders Library – (company name)”.

Security POCs:

Mr. Steven Mafla Ms. Rebecca Williams

SSC/SZ SSC/SZ

Email: steven.mafla.ctr@spaceforce.mil Email: rebecca.williams.4.ctr@spaceforce.mil

Submit the following information for security verification:

• Submitter’s name and parent company (if applicable)

• Mailing address/facility: street address, city, state, nine-Digit zip code

• CAGE code

• UEI

• Any active Government contract number If the prospective Offeror doesn’t have an active Government Contract Number, the following must be submitted from the company’s Facility Security Officer (FSO):

A FSO signed letter on company letterhead confirming: 1. eligibility to receive CUI and

2. CUI data handling and storage is in place

• POC name, telephone number, and email address

4. Vetting and Approval The Government representative will review the submitted information to confirm that the company meets the required access criteria, IAW regulations like the NISPOM and relevant CUI rules. Requests that do not include the required Contractor verification information will be denied.

5. Secure Document Transmission Once a Contractor is vetted and approved, the CUI document will be sent via DOW Secure Access File Exchange (SAFE). The Contractor POC will receive two emails: 1. with a link to the online secure pickup location and claim code and 2. with a passphrase for access to the encrypted file.

6. Required Protection of the Document After receiving the CUI document, the contractor is responsible for protecting it according to CUI policy. CUI must be handled and stored on systems that align with minimum security requirements, such as those specified in the NIST SP 800-171.

8.1.1 CUI Solution Brief / Pitch Day Submission Instructions

If you plan on submitting a CUI Solution Brief / Pitch Day for the SDN-B MOC CSO, you may ask for the DOW SAFE "Request a Drop-Off" link up to 14 calendar days prior to your planned submission date and NLT noon Thursday, May 14, 2026. For your awareness, the link may only be used once and expires after the Drop-off has been completed.

To request the DOW SAFE Submission Link, send an email to both security POCs (listed below) with the subject line “SDN-B MOC CSO DOW SAFE Request– (company name)”.

Security POCs:

Mr. Steven Mafla Ms. Rebecca Williams

SSC/SZ SSC/SZ

Email: steven.mafla.ctr@spaceforce.mil Email: rebecca.williams.4.ctr@spaceforce.mil

5.12 Step 3: Full Proposal (by invitation only)

6.3 Step 3 Evaluation Factors