Attachment 2 - Draft T1 OandI Proposal Instructions.pdf

HQ085022R0002 Attachment 2 i

National Defense Space Architecture

Tranche 1 Operations and Integration

Proposal Instructions

1 November 2021

DISTRIBUTION STATEMENT A: Approved for public release: distribution unlimited.

ii

Table of Contents

Introduction

Submission Instructions

Proposal Format Instructions

Use of Non-Government Advisors

Definitions

Volume I: Executive Summary

Volume II: Management Approach

Program Management

First 100 Days

Subcontractor and Supply Chain Management

Systems Engineering

Organizational Conflict of Interest

Personnel Résumés

Personnel Matrix

Technical Data and Computer Software Rights Assertions

Operations, Maintenance and Sustainment Plan

Volume III: Schedule and Schedule Management

Integrated Master Schedule (IMS)

Schedule Management

Volume IV: Technical Solution

System Architecture

System Operations Concept (OPSCON)

Facilities Development

SUPERNOVA Development

Development, Operations, Maintenance and Sustainment Tool Suite

Integration and Test

Ground Entry Points (GEP) Acquisition

Radio Frequency (RF) (Mil Ka and Mil S) Antennas

Optical Ground Terminal (OGT)

Volume V: Past Performance and Experience

Volume VI: Small Business Participation

Volume VII: Cost/Price and Rationale

Contract Line Item Number (CLIN) Structure iii

Fixed Price Milestone Payments

Cost Narrative

Proposal Pricing Detail

Cost Build Up

Direct Labor

Travel, Equipment, Material, and Other Direct Costs

Teammate Proposals

Pricing Data by Contract Line Item Number (CLIN)

Introduction

The Offeror shall propose to design, develop and deliver the Tranche 1 (T1) Operations and

Integration (O&I) via seven (7) volumes. Specific volume with associated page limits are detailed below.

Volume I: Executive Summary page count limit is 5 pages.

Volume II: Management Approach page count limit is 20 pages.

Volume III: Schedule and Schedule Management page count limit is 10 pages of content and unlimited for the IMS file.

Volume IV: Technical Solution page count limit is 30 pages.

Volume V: Past Performance and Experience page count limit is 10 pages.

Volume VI: Small Business Participation page count limit is unlimited.

Volume VII: Cost/Price and Rationale page count limit is unlimited.

Proposals must be clear, concise, and include sufficient detail to support a thorough and effective evaluation. Offerors are CAUTIONED not to simply rephrase or restate the Government’s requirements. Proposals MUST provide convincing rationale supported by factual, verifiable information that fully demonstrates that the Offeror understands the requirements outlined in the

SOW for this acquisition. Proposals must clearly describe how the Offeror intends to fully satisfy these requirements. The Offeror should assume the Government has no prior knowledge of its capabilities and experience, and will base its evaluation solely upon the information presented in the Offeror’s proposal except for Past Performance and Small Business.

The Offeror shall provide tailored T1 O&I processes and procedures including stakeholders, teammates, subcontractors, and associate contractors for all inputs.

Submission Instructions

The Space Development Agency (SDA) requests that Offerors submit only electronic proposals.

All Volumes along with any appendices and/or attachments shall be submitted only in .pdf format and must be submitted independently by file as SDA will not accept .zip files. Offerors shall submit their responses via Department of Defense (DoD) Secure Access File Exchange (SAFE):

https://safe.apps.mil. Offerors shall submit one (1) original copy of each Volume and appendices and/or attachments to be used for any and all printing or official copy retention requirements and one (1) additional copy of each Volume and appendices and/or attachments NO LATER THAN

1600 EDT 16 February 2022. Each Volume shall be submitted as a separate .pdf file. Offerors shall submit each copy of their proposal via a separate DoD SAFE submission and all files should be included in a single DoD SAFE submission. Each file submitted must be clearly labeled with the SDA Request for Proposal (RFP) number, prime contractor organization name, prime contractor proposal title (short title recommended), and Volume number and appendix or attachment number (as appropriate). The size limit for each SAFE file transmission is 8192 MB.

Proposals submitted shall not exceed the CUI level and shall be appropriately marked in accordance with DoD Instruction 5200.48 – Controlled Unclassified Information, dated March 6, 2020, if CUI is present.

SDA assumes all responses are no higher than CUI. Offerors shall request a SAFE Drop-off

Request, via an email to osd.pentagon.ousd-r-e.mbx.hq085022r0002@mail.mil, NO LATER https://safe.apps.mil/ mailto:osd.pentagon.ousd-r-e.mbx.hq085022r0002@mail.mil

THAN 1200 EDT 9 February 2022. The Offeror shall request a SAFE Drop-off Request regardless of whether or not they have access to DoD SAFE already. The subject line shall be: O and I RFP

Submission SAFE Request (m of n) and the Offeror’s organization name, where m is the request number and n is the total number of requests that will be made by the Offeror. If the Offeror’s submission will exceed the DoD size limit, then they shall make the required number of requests to complete their submission. Within the body email, the Offeror shall clearly state the email address to which the Drop-off Request will be sent. The Offeror is free to request read receipts for each Drop-off Request email sent. The Offeror will receive an email with their SAFE Drop-Off

Request NLT 1200 EDT 15 February 2022. Note that this email will not come from the email address listed above.

Within the DoD SAFE submission form, the Offeror shall check both the “Encrypt every file” check box and the “Send me an email when each recipient picks up the files” check box. The password shall be sent under separate email to the email address above with the subject line: O and I RFP Submission SAFE Request (m of n) Password and the Offeror’s organization name. The

“Short note to the Recipients” field shall clearly identify the Offeror’s organization name, the proposal name, and the number of the submission.

SDA does not anticipate classified responses to this RFP. However, if deemed necessary to adequately describe classified aspects of the Offerors’ Past Performance (only), a separate classified attachment (not to exceed 10 pages) may be submitted. Submissions shall not exceed the SECRET collateral level. Offerors desiring to submit classified Past Performance attachments must ensure the information is appropriately classified and marked in accordance with the appropriate security classification guidance. Offerors must contact SDA via the email address above for classified Past Performance submission instructions. Classified submissions via

SIPRNET, JWICS, or secure fax are not authorized.

Proposals received after 1600 EDT 16 February 2022 will be considered late and not evaluated. Offerors whose proposals which are considered late will be so informed by the primary contracting officer (PCO) and their proposals will be deleted without any files being opened or read.

Proposal Format Instructions

The font in normal text for all volumes shall be no smaller than Times New Roman 12 pt., while text in tables and figures shall be no smaller than Times New Roman 10 pt. All margins (top, bottom, left, and right) shall be no smaller than one (1) inch. All .pdf pages, in all volumes, formatted larger than 8.5 inches X 11 inches shall be counted as two (2) pages. Line numbers shall be applied to all text sections in all volumes and shall be set within the left margin of the page so as not to reduce the usable size of the page. Title pages and tables of contents, tables of figures and/or tables will not count against the page counts of the respective volumes and will not be evaluated for content. Note: Nonconforming proposals may be rejected without review.

Use of Non-Government Advisors

The Offeror is advised that technical and price data submitted to the Government in response to this solicitation may be released to non-Government advisors that have signed non-disclosure agreements (NDAs) for review and analysis. Any objection to release shall be provided in writing to the Contracting Officer (CO) within ten (10) days of the RFP issuance and shall include a detailed statement of the basis for the objection. The detailed statement shall identify the specific portions of the proposal which the Offeror objects to disclosure to non-Government advisors.

Definitions

Within this Attachment, the following definitions are used:

T1TL SVs: Baseline Tranche 1 Transport Layer space vehicles (SVs) deployed into a nominal six-plane constellation consisting of 126 SVs in total.

T1DES SVs: Tranche 1 Demonstration and Experimentation System SVs that host demonstration payloads and experimental payloads developed through SDA’s Partner

Payload Program (P3). The nominal T1DES constellation consists of up to 18 SVs deployed into similar orbits and connected to the T1 system.

Ground Segment (GS): The NDSA Ground Segment is comprised of two Operations

Center facilities, all internal and external ground communications interfaces, and RF and optical GEPs supporting the T1 foundational capabilities.

Operations Center (OC): The SDA Operations Centers are the physical facilities that contain all hardware, software, and personnel required to operate the T1 system.

NEBULA Operations – Vendor Architecture (NOVA): Hardware and software required for each SV vendor to perform highly automated constellation and network operations of their own SVs from the SDA OCs. A separate NOVA is developed, delivered, and operated by each T1TL, T1DES, and T1 Tracking Layer SV vendor.

SDA Unified Planning Environment and Resources for NEBULA Operations –

Vendor Agnostic (SUPERNOVA): Hardware and software required for integrated T1TL network and mission operations from the SDA OCs.

Ground Entry Point (GEP): A terrestrial station designed for communicating with the

SVs via RF or optical communications.

Enterprise Management: Activities such as providing the enterprise messaging services, management and monitoring of system-wide hardware, software and security services, monitoring the SV constellation’s state of health, and interfacing with external networks for data ingest and distribution.

Network Management: Activities such as creating and implementing a network topology and monitoring network performance, based on the SV’s mission plan, which is the scheduled sequence of service requests assigned to each SV to fulfill.

Mission Management: Activities such as creating a mission plan for each of the SVs based on an input list of Enterprise-wide service requests, where a service request is a request for

T1 to create a connection to an external system or to perform a specific activity, to include items such as connecting to Link 16 networks, connecting to Ka-band GEPs, connecting to

Ka-band tactical users, connecting to Optical Communications Terminals (OCTs) that are not part of the T1 constellation, and performing Position, Navigation and Timing (PNT)

Situational Awareness (SA) collections. Mission Management covers scheduling of SV and ground resources, SV command encapsulation for data distribution, Enterprise-wide initial maneuver management assessment and distribution to associated NOVA systems for higher fidelity assessment coupled with GEP tracking services management and monitoring.

Constellation Monitoring: Activities such as constellation-wide ephemerides reporting, contingency operations, anomaly resolution, RF interference resolution, and collision avoidance.

Prime: The O&I Offeror.

Major Teammate: A member of the Prime's development team with a different

Commercial and Government Entity (CAGE) code from the prime Offeror, that either accounts for no less than ten (10) percent of the proposed cost and/or the develops one of the following subsystems:

o SUPERNOVA o Networking and Data Routing o Encryption o RF Antennas o Optical Ground Terminal (OGT) o Interoperability Testing

Volume I: Executive Summary

Volume I shall not exceed five (5) pages. Any pages in excess of this limit, other than those noted below as specifically excluded from the overall page limit, will be removed from the

Offeror’s proposal and not evaluated.

The Executive Summary shall contain an overview of the governance and program management approaches, the technical solution, and the Offeror’s past performance.

The Offeror shall identify their program team, including contributions of each major teammate, and shall provide a summary of the past performance of themselves and each major teammate. The

Offeror shall include an organization chart depicting their key personnel and major teammates.

The Offeror shall include a schedule of key program milestones.

The Offeror shall include an overview of their system architecture including an Operational

Viewpoint (OV)-1 level diagram of the architecture.

Volume II: Management Approach

Volume II shall not exceed twenty (20) pages. Any pages in excess of this limit, other than those noted below as specifically excluded from the overall page limit, will be removed from the Offeror’s proposal and not evaluated.

Program Management

The Offeror shall provide a detailed description of the Offeror’s proposed program management processes, procedures, methods, and tools for executing the program on schedule and within the price proposed. The Offeror shall describe how they use these processes, procedures, methods, and tools to manage the life cycle of large, complex systems.

The Offeror shall discuss their program, personnel, organization chart, cost, and risk management approach and their processes and tools for executing the program on schedule and within the price proposed. The Offeror shall include a list of the primary risks on the project, the planned mitigations, and the approach for managing risks throughout the system life cycle.

The Offeror shall describe its processes for staffing the program with qualified personnel, communicating plans and status to the customer, identifying and managing critical vendors and subcontractors, and controlling costs within a cost plus price environment. The Offeror shall document planned communication with the Government, detailing the purpose, entrance criteria, key accomplishments anticipated, exit criteria, and documentation methodologies for each meeting, review, or key management milestone within the program.

The Offeror shall plan the program using the milestones identified in Attachment 1 – Statement of

Work and Technical Requirements Document. If the Offeror believes that an alternate review structure (e.g., combining certain reviews) meets the needs of the Government for insight into the design and understanding of challenges and risks at appropriate stages of the development, the

Contractor is free to propose it. For each review combined, omitted, or added, the Contractor shall clearly delineate during what remaining review(s) the information traditionally provided shall be discussed.

First 100 Days

The Offeror’s proposal shall specifically identify key activities they intend to perform in the first

100 days to ensure the greatest possible chance of program success. The Offeror shall describe the importance of their selected activities, their approach for execution, and the direct impacts those activities will have in successful initiation and execution of their program scope of work. These activities shall be included in their program plan and shall include the following:

Addressing technical and schedule risks with proactive burn down plans

Staffing, by name and by labor category, against critical work packages

Subcontracting actions to be executed with whom, by when, and priority rationale

Identification of long lead procurement items and their supply chain procurement schedules

Travel, including personnel, destination, and purpose

Program tailored security processes

Integrated architecture and operational concepts definition

Establishment of interface working groups and applicable teaming arrangements

Any other specific activities the Offeror deems necessary upon initiation to assure program success

Subcontractor and Supply Chain Management

The Offeror shall address their subcontractor and supply chain management methodologies. The

Offeror should describe how they will minimize the impact of fluctuations in supply chain availability and subcontractor deliveries on program execution. The Offeror shall describe long-lead items and impacts on the proposed integrated master schedule. The Offeror shall explain their approach to ensuring supply chain integrity for all hardware, firmware, and software delivered and/or integrated by the Contractor.

Systems Engineering

The Offeror shall detail the Systems Engineering processes and methods that will be used to execute the O&I program and how the stakeholders, teammates and subcontractors are integrated into these processes and methods. The Offeror shall clearly identify their approach to systems engineering and detail the use of any processes and tools that will be used on the program. The

Government expects that the Offeror will utilize Systems Engineering best practices. The Offeror shall provide a Document Tree for the O&I program. The Offeror shall describe Trade Studies and

Analyses upon request with an estimated Trade Study or Analysis to occur once per quarter for the

Period of Performance (PoP). as an exemplar of the Trades and Analysis

2.1.3.1 Cloud vs Stand-alone Trade Analysis

The Offeror shall provide the Government with their trade-analyses for a cloud based system vs a stand-alone system, listing key advantages and disadvantages for their proposed system configuration including cost, schedule, and technical factors (Cloud vs Stand-alone). This analysis should describe the considerations and conclusions for the proposed design and meeting the stated requirements. This analysis is limited to five (5) pages. Any pages beyond the limited will be removed from the volume and will not be evaluated.

Organizational Conflict of Interest

(a) There is potential organizational conflict of interest (see FAR Subpart 9.5, Organizational and

Consultant Conflicts of Interest) due to the nature of separate solicitations and contracts for an integrated Tranche 1 system of systems. Reference PotentialOCI.xlsx within the Bidder’s Library for initial OCI impact assessments. At this time the Government is chiefly concerned about future potential OCI issues between the prime contractor for the T1 Operations & Integration contract and the prime contractor for any T1 space vehicle development contract, such as those for T1

Transport Layer (T1TL). As a part of the proposal, the Offeror shall provide the contracting officer with complete information of previous, potentially impending, or ongoing work that is in any way associated with the contemplated acquisition.

(b) If award is made to the Offeror, the resulting contract may include an organizational conflict of interest limitation applicable to the related Government work, at either a prime contract level, at any subcontract tier, or both. During evaluation of proposals, the Government may also, after discussions with the Offeror and consideration of ways to avoid the conflict of interest, insert a special provision addressing eligibility for future contract awards within the existing tranche.

(c) The organizational conflict of interest clause included in this solicitation may be modified or deleted during negotiations.

(d) The Agency reserves the right to waive an OCI that is in the best interests of the government.

If the Offeror believes that an OCI exists or may exist upon award, then the Offeror shall include an OCI mitigation plan as an appendix to this volume. The OCI mitigation plan will not be included in the Volume II page limit.

Personnel Résumés

Personnel résumés shall not exceed two (2) pages each. The personnel résumés shall be included as attachments to this volume and will not be included in the Volume II page limit.

The Offeror shall identify the key personnel planned to be assigned to this program from the

Offeror and major teammates and subcontractors as appropriate. Résumés should be in bullet format and include:

Summary statement highlighting experience and expertise

Current role with the Offeror or teammate to include current assignments and programs

Planned role within the T1 O&I program

Evidence of applicable mission experience or understanding

Education (academic and military, if applicable)

Military, Government, or Commercial space-related experience (if any)

Anticipated percentage of time to be assigned to this program

Signed statement agreeing to support the SDA T1 O&I program if awarded

Proposed staff members not currently employed by the Offeror may be included as appropriate. In those cases, the Offeror shall include signed contingent offer letters. These letters should be signed by both the Offeror and the proposed staff member and should state the willingness of the proposed staff member to join the Offeror in support of the SDA T1 O&I program if awarded.

At a minimum, the résumés shall include the following key personnel from the Offeror:

Program Manager

Chief Engineer

ISSM

Development Lead Engineer

Operations Lead

Interoperability/Integration and Test Lead

Maintenance Lead Engineer

Personnel Matrix

The personnel/ matrix shall be submitted as an attachment to this volume and will not be included in the Volume II page limit.

The Offeror shall compare and contrast their submitted personnel résumés against the SDA T1

O&I requirements to validate corporate and individual experience and expertise thereby giving

SDA confidence in the Offeror’s probability of success. Format for this comparison is entirely up to the Offeror but this section of the proposal should stand alone for evaluation.

Technical Data and Computer Software Rights Assertions

The Offeror shall clearly delineate all limitations on data, hardware, and computer software rights for technical data, hardware, or computer software provided by the Offeror and all of its teammates, using the format shown in Table 1. It is the Government’s assumption that no hardware, technical data or computer software will be provided with less than Government

Purpose Rights (see DFARS 252.227-7013, 7014, 7015) and that the vast majority of information generated will be provided with Unlimited Rights to the Government. The Offeror shall clearly identify those elements to be provided with less than Unlimited Rights and identify the rationale for their assertion(s) using the format shown in Table 1. Any item related to the performance of this effort and not contained in Table 1 shall be delivered upon request to the Government, with no less than Government Purpose Rights.

Table 1: Technical and Data Rights Assertion Template

Company

Asserting

Data Rights

Hardware/Technical

Data/Computer Software to be Furnished with

Restrictions

Summary of

Intended Use in the Conduct of the Effort

Basis for

Assertion

Asserted

Rights

Category

Name of

Person

Asserting

Restrictions

(NAME) (LIST) (NARRATIVE) (LIST) (LIST) (LIST)

Table 1 shall be included as an attachment to Volume II and will not be included in the page count. Any associated text will be included in the page limit.

Operations, Maintenance and Sustainment Plan

The Offeror shall discuss their program, personnel, cost and risk management approaches, process and tools, specifically focused on operations, maintenance, and sustainment. The Offeror shall describe the operations structure, staffing including their expected staffing profiles for teams within the associated facilities and across appropriate system phases, and their approach to maintaining and training qualified personnel throughout the project period. The Offers shall discuss a sparing philosophy for the program. The Offeror shall include a list of the primary risks on the project, the planned mitigations, and the approach for managing risks throughout the system life cycle for operations through sustainment. The Offeror shall describe their personnel, DevSecOps techniques, tools, and approaches for sustaining the GS in accordance with the requirements in Attachment 1 – Statement of Work and Technical Requirements Document.

Volume III: Schedule and Schedule Management

Volume III shall not exceed ten (10) pages. Any pages in excess of this limit, other than those noted below as specifically excluded from the overall page limit, will be removed from the

Offeror’s proposal and not evaluated.

Integrated Master Schedule (IMS)

The Offeror shall present a milestone-driven IMS designed to meet the Government’s notional milestones provided in Attachment 1 – Statement of Work and Technical Requirements Document.

The Offeror should identify major reviews and program milestones including T1TL milestones, and include entrance criteria, key accomplishments, and exit criteria for each milestone, including significant reviews and integration and test activities. At least two of the pages should be a separable, standalone detailed Gantt chart (or similar illustration) clearly presenting the Offeror’s milestone-driven integrated master schedule. This chart should include external dependencies, integration specific tasks, assumed Government or subcontractor hardware, software, or information deliveries and/or approvals, interoperability tests, demonstrations, reviews, milestones, and/or any other key activities in the Offeror’s proposed program.

The Offeror shall clearly delineate the primary and secondary critical path within their schedule, from contract award through operations and sustainment, and any additional critical paths deemed appropriate to justify their ability to deliver the proposed Operation Centers and SUPERNOVA on time and on cost. The Offeror should discuss the critical path analysis used to determine the primary and secondary critical paths. The Offeror should discuss their approach to managing progress against the baseline schedule.

The Offeror shall also identify the top schedule risks in executing the O&I effort and outline their mitigation approaches to ensure on time delivery. The Offeror shall include their plans to minimize the risk associated with working with multiple contractors to ensure the Ground Segment is ready prior to the Ground Readiness Review (GRR). The Offeror shall include a schedule risk assessment and margin evaluation.

The Offeror shall deliver their complete IMS in Microsoft Project-compliant native format as well as .pdf format in conjunction with this volume. The complete IMS shall include schedule details down to at least Level 3 of the work breakdown structure (WBS). The delivered IMS files

(Microsoft Project and .pdf format) will not count against the Volume III page limit, however, the

Gantt chart is included in the page limit.

Schedule Management

The Offeror shall describe their approach to managing dynamic schedules with varying levels of task order definitization for T1 NDSA design, development, integration, and operations, including but not limited to lines of effort from the Offeror, T1TL contractors, BMC3 contractor and the

T1DES contractor. The Offeror shall present their approach to identifying and addressing evolving schedule risks as T1 contract activities progress and describe how their approach to addressing schedule risks maximizes the probability of delivering the T1 NDSA on schedule.

Volume IV: Technical Solution

Volume IV shall not exceed thirty (30) pages. Any pages in excess of this limit, other than those noted below as specifically excluded from the overall page limit, will be removed from the Offeror’s proposal and not evaluated.

System Architecture

The Offeror shall present the system architecture subsystem including system, and subsystem functional flow block diagrams for operating the NDSA Ground Operations Center in compliance with the requirements as presented in Attachment 1 – Statement of Work and Technical

Requirements Document. The Offer shall identify required interfaces and interface mechanisms, both internal to SDA to external customers, the Operations, Maintenance, and Sustainment (OMS)

Tool Suite, and internal and external services. The Offeror shall define what functions the ground segment and mission operations are assumed to provide. The Offeror shall provide a description of the cybersecurity services solutions of the SUPERNOVA ground system.

System Operations Concept (OPSCON)

The Offeror shall submit a draft a Draft System Operations Concept (OPSCON) (CDRL 021) describing the personnel, techniques and procedures that will be used for conducting the operations and maintenance of the Operation Centers and GEPs. The Offeror shall include a two (2) page detailed architecture diagram for the entire T1 system and a five (5) page day-in-the-life (DITL) narrative during the “Walk” mission phase. The diagram shall clearly delineate the major system components and their functions. The diagram should indicate and specify any interfaces between any of the system components and/or personnel. The diagram should indicate which system (SYS) requirements are allocated to each system components. The diagram should indicate which of these system components are assumed as Government-Furnished Equipment, Commercial-Off-The-

Shelf products acquired by the Offeror, Offeror in-house tools or products adapted for use in T1, or new development items. For any of the non-GFE, the diagram should indicate the level of data rights asserted. For any Offeror in-house tools or new development items, the Offeror should indicate if it is provided or developed by the Offeror or by a teammate and, if so, which teammate.

The accompanying narrative shall describe an operational day-in-the-life during the “Walk” mission phase, from the receipt of a service request by a tactical user to confirmed satisfaction of the service request. The narrative shall describe all tasks or activities required to successfully execute, which system components or personnel are performing those tasks or activities, and description of the interactions between them. The narrative shall indicate any assumed

Government approvals required throughout the process.

Facilities Development

The Offeror shall define the facilities that will be used to support operations, the design, configuration, and manning (crew mix and skill set) of the OCs to allow for 24/7 autonomous operations. The Offeror shall include their architecture diagrams and physical layout of the two operation centers: operations floor, staffing (crew mix and skill sets) to include roles and responsibilities for the different positions, equipment (hardware and software) and the network connections required. The Offeror shall clearly identify the ability of their facilities to support operations at the multiple classification levels. The Offeror shall provide a detailed description of how they will maintain proper physical and logical security protocols to ensure only authorized personnel have access to the facility, system hardware and software components. The Offeror should describe the systems and approach for access control and inventory control.

SUPERNOVA Development

The Offeror shall describe their technical approach for developing and delivering their

SUPERNOVA system that meets all applicable requirements in Attachment 1 – Statement of

Work and Technical Requirements Document. The Offeror shall include their SUPERNOVA system architecture and design diagrams to include a functional block diagram showing the products and services being used within their solution. The Offeror shall describe their approach for applications and services compatible with Enterprise Ground Services (EGS) products and services into their SUPERNOVA solution. The Offeror shall provide a detailed description of how

Transport Service Requests are submitted, received, processed, and acted upon, to include acknowledgement of the request, implementation, and execution of the task(s). The Offeror shall present their considerations for their data storage implementation (on-site, cloud-based or hybrid solution).

Development, Operations, Maintenance and Sustainment Tool Suite

The Offeror shall provide a detailed description of their Development, Operations, Maintenance and Sustainment tools including the following:

Tool maturity in similar environments

Native interface capabilities

Native user interfaces and automation capabilities

Processing requirements such as CPU, RAM, and storage requirements

Native scalability

Native interoperability within an Enterprise system

Licensing requirements

The Offeror should clearly identify any mission constraints or limitations of the proposed

Operations and Maintenance tools. The Offeror shall describe the enterprise system Common

Operational Picture (COP) approach. The Offeror shall describe their use of Commercial off-the-shelf (COTS) software and tools.

Integration and Test

The Offeror should describe their complete hardware, software test and integration approaches, methodologies, performance, verification, documentation, and staffing. The Offeror shall present their approach/method for implementing DevSecOps, providing an environment to allow for continuous development, integration, testing, and deployment of capabilities. The Offeror should discuss their methods, software suite, and tools for integrating / interfacing with SV NOVAs, BMC3, and the GEPs. The Offeror should define the verification and interoperability tests and tools that they plan to perform and use and the benefit that those tests and tools will bring to SDA.

Of particular interest to SDA is the Offeror’s approach to conducting tests and demonstrations in concert with the SV contractors prior to launch and during early orbit operations and checkout.

Throughout the discussion of their test activities, Offerors should clearly identify manual, automated, live, virtual, and constructive tests and demonstrations, if applicable, and any elements expected to be provided by the Government to facilitate completion of their verification program.

Ground Entry Points (GEP) Acquisition

The Offeror shall describe their technical approach for GEP acquisition and delivering solutions that meets all GEP requirements in Attachment 1 – Statement of Work and Technical

Requirements Document. For each GEP below, the Offeror shall include, but not be limited to: a discussion of hardware, software, control, data transfer capability and/or limitations, environmental and power requirements. The Offeror shall address any needed test and certification requirements and plans and must include schedule and risk assessments for subject completion.

Radio Frequency (RF) (Mil Ka and Mil S) Antennas

The Offeror shall provide their technical approach for procuring, installing, testing, and delivering of ten radio frequency (RF) (8 Mil Ka and 2 Mil S) antennas into operations, at multiple locations.

The Offeror shall identify the number of terminals, frequency of operation, bandwidth, anticipated power requirements, anticipated data rate, bit error rate, and any other parameters key to mission performance. The Offeror should identify the antenna configurations, field of regard, and deployment mechanisms for each of the antenna systems. The Offeror shall include a description of the space to ground communications solution to accomplish checkout and testing of the antennas. The Offeror should provide an estimate of the duty cycle required of each ground antenna to support the T1 Space Segment.

Optical Ground Terminal (OGT)

The Offeror shall provide their technical approach for procuring, installing, testing, and delivery of one OGT to Kirtland AFB, NM. The Offeror shall assume a GFE OGT design providing a detailed description of the optical ground terminal. The Offeror should identify the anticipated environmental, power requirements, data rate, bit error rate, and any other parameters considered key by the Offeror. The Offeror shall identify the compliance of their current system with the SDA

T1 OCT Standard, detail any non-compliant components of their design, and describe the path to full compliance for those components.

Volume V: Past Performance and Experience

Volume V shall not exceed ten (10) pages inclusive of all unclassified or classified pages. Any pages in excess of this limit, other than those noted below as specifically excluded from the overall page limit, will be removed from the Offeror’s proposal and not evaluated.

The Offeror should introduce the current and past performance citations, clearly stating why they have chosen the efforts and how they best prove their ability to perform the proposed workscope.

They should include experience in developing an OC, experience in Low Earth Orbit (LEO) satellite constellation monitoring and control, and experience working with multiple SV providers. Each citation should provide specific, measurable validation of the Offeror’s rationale and document successful current and past performance directly relevant to the current solicitation.

The Government expects direct correlation between the current and past performance citations and the résumés submitted in Volume II – Management Approach.

The Offeror shall include information on recent/current programs that are similar in magnitude, scope, and complexity to this program. These submissions should clearly demonstrate the ability of the Offeror and its teammates to satisfy the totality of the T1 O&I requirements. The minimum set of major teammates is defined in the introduction to this Attachment. All submissions shall have a period of performance within three (3) years from the proposal due date.

For each submitted citation, the Offeror shall identify:

Customer (Name, phone, email, affiliation)

Scope to include number of OCs delivered, experience working with multiple SV providers, and experience in LEO satellite constellation monitoring and mesh network management

Place of performance, period of performance, contract/agreement type

Bid cost/price, currently invoiced cost/price, Final price/Estimate at Completion

Specific rationale for effort selection and detailed justification of relevance

The Offeror is highly encouraged to use key graphics to convey important elements of their current and past performance. High level graphical descriptions of the operational concept (e.g., Department of Defense Architecture Framework’s (DoDAF’s) OV-1) depicting numbers and locations of OCs, Gantt charts showing key program milestones planned and achieved, Earned

Value charts (if applicable) showing estimates and current status, etc. are all substantially more valuable to the Government for relevance evaluation purposes than detailed written explanations.

These artifacts should be taken directly from the efforts cited and be suitable for use by the

Government in conjunction with interviews which may be conducted with the customers named in each citation. Project citations shall not exceed four (4) pages each and should stand alone by project.

Separately from the above examples, each Offeror shall submit past performance information to demonstrate compliance with the requirements of FAR Subpart 52.219-9, Small Business

Subcontracting Plan including the extent to which applicable goals and other small business performance objectives/requirements were met for the contracts submitted to demonstrate compliance. For past performance efforts where minimum quantitative requirements and/or goals were not met, explanation of efforts to resolve the issue(s) must be provided. In sum, the response to this paragraph shall not exceed two (2) pages in addition to the 10 pages allocated to this section.

Current and Past Performance citations shall only include work that has been completed or is ongoing. If a citation indicates expected capability, such as a program that has yet to be launched, only the work completed to date will be evaluated.

Offerors are hereby notified that SDA intends to survey Contractor Performance Assessment

Reports (CPARs) and to conduct interviews with customers identified in Volume V. Information obtained via either of these methods will be included in Offeror evaluations per the criteria in

Attachment 3 – Evaluation Factors for Award of this RFP.

Volume VI: Small Business Participation

There is no page limit for Volume VI. Content in Volume VI will only be evaluated in support of the Small Business Utilization Factor and will not be evaluated for other technical content.

The Offeror shall submit a Small Business Utilization Plan (SBUP) and/or Small Business

Participation Commitment Document (SPCD) (see Attachment 4 – SBPCD) detailing their anticipated small business inclusion for this procurement to include selection, integration and evaluation processes. While SDA will not mandate specific percentage goals by individual small business type, the Offeror must meet the Minimum Quantitative Requirement (MQR) of small business participation which is five (5) percent of the total proposed contract value (to include options). The Offeror shall detail planned small business contribution by type (Woman-Owned, Disadvantaged, Veteran-Owned, Service Disabled, etc.) and by type of work expected to be performed (administrative, engineering, assembly, test and evaluation, modeling and simulation, etc.). The Government expects that significant engineering and technical elements of this procurement will be contributed by other than traditional large aerospace and defense contractors, including but not limited to new and emerging small business.

Volume VII: Cost/Price and Rationale

There is no page limit for Volume VII. This volume consists of relevant information describing the Offeror's proposed cost/price for meeting solicitation requirements.

The Offeror's proposal shall contain sufficient factual information to establish the realism and reasonableness of the proposed cost, see Attachment 3 – Evaluation Factors for Award. The

Offeror shall detail their assumptions, basis of estimates, and rationale supporting their proposed cost and pricing. This information will be used to evaluate the risks associated with the proposed technical solution, schedule, and price.

Contract Line Item Number (CLIN) Structure

The Government anticipates awarding the Contract Line Item Numbers (CLINs) as shown in Table

2. All CLINs shall be included for a compliant proposal.

Table 2: CLIN Definitions

CLIN Description Details Contract

Type

CLIN Start/Stop

Development and

Integration (primary

CLIN)

Design, development, integration and delivery of 2 integrated operations centers with development, test and integration capabilities and external interface connectivity.

CPFF Authorization to Proceed

(ATP)/GRR

Operations, Maintenance, and

Sustainment (base period)

All Operations, Maintenance, and

Sustainment activities for the GS for the first 2 years

FFP ~6 months prior to GRR/ end of fiscal year (EOFY) year 2026

3-5

Operations, Maintenance, and

Sustainment

Options (CLIN for each of up to 3 option years)

All Operations, Maintenance, and

Sustainment activities for the GS for the years 3-5

FFP EOY 2026/EOFY 2027;

EOY 2027/EOFY 2028;

EOY 2028/EOFY 2029;

Tracking Layer

(Option)

Tracking Layer addition to existing baseline

CPFF TBD/TBD

T1DES (Option) T1DES addition to existing baseline

CPFF ATP (TBD)/GRR (TBD)

Fixed Price Milestone Payments

The Government intends to fund fixed price CLINs via event-based Milestone Payments. For each milestone payment, the Offeror shall specify the payment amount, terms, conditions, Government acceptance criteria, and percentage of the total CLIN price.

Table 3: Fixed Priced CLIN Milestone Payments

CLIN Description Milestone Payment Percentages

2 Operations, Maintenance, and Sustainment

(base period)

Equal quarterly payment based upon Government approved content in sustainment delivery drop

3-5 Operations, Maintenance, and Sustainment

(CLIN for each of up to 3 option years)

Equal quarterly payment based upon Government approved content in sustainment delivery drop

9 GEP Operations and Maintenance (base period)

Equal monthly payment

10-12 GEP Operations and Maintenance Options

(CLIN for each of up to 3 option years)

Equal monthly payment

Cost Narrative

In this section, the Offeror shall describe the underlying methodology used in its submitted cost template. Items that shall be addressed include, but are not limited to, the following:

1. Provide a listing of company labor categories, position codes, or designators, and definitions of those proposed categories for the Prime and each subcontractor.

2. The Offeror shall identify the basis of direct labor rates (e.g., forward pricing rate agreement or forward pricing rate proposal or forward pricing rate recommendation). The use of composite rates is strongly discouraged and should be avoided.

3. Identify, in full detail, all internal bid codes and burden centers corresponding to each labor category if applicable.

The cost narrative shall include an Executive Summary that presents an overview of the Offeror’s proposal. An effective Executive Summary will function as a proposal roadmap, and will help the

Government evaluator understand the Offeror’s overall approach to pricing the requirements of the RFP. The Executive Summary should highlight the proposal’s pricing development and any significant cost elements impacting the proposed price. Describe all key ground rules and assumptions used in the development of the proposed costs. For example, resources required of the Government (e.g., Government-furnished equipment and property, including estimated costs if required for Offeror’s technical approach).

Proposal Pricing Detail

The Offeror shall provide the total price and elements of price broken down by the Contract Work

Breakdown Structure (CWBS), milestone payment schedule, and by Government Fiscal Year. For the purposes of Executive Summary pricing, the Offeror shall assume that the SDA Operations

Centers are located in North Dakota and Alabama.

The cost shall be broken down by work breakdown structure (WBS) task and Government Fiscal

Year (GFY) using the template in Table 4. The price shall be provided for items down to Level 3 of the CWBS for each GFY.

Table 4: Projected Costs by GFY C

L

IN

W B

S

W B

S

E le m en t

G F

Y

G F

Y

Y

Y

Y

Y

Y

Y

T o ta l

The Offeror shall minimally include in this section:

1. A summary of projected funding requirements by quarter for each GFY to enable fiscal and milestone payment planning.

2. Price and percentage of price by the prime and major teammates, where the minimum set of major teammates is defined in the introduction to this Attachment.

3. Identification of pricing assumptions of which may require incorporation into the resulting award instrument (e.g., use of Government Furnished Property/Facilities/Information, access to Government Subject Matter Experts, etc.) for all members of the team.

Cost Build Up

This section shall contain a summary of labor hours, direct and indirect rates, and other information supporting the proposed costs. Items addressed shall include, but are not limited to the following:

1. Offerors shall provide unsanitized cost breakdown(s) in accordance with FAR 15.408

Table 15-2.

2. The Government will use Microsoft Office 2016 Excel for evaluation and analysis of the cost section of the Cost Volume. The Excel spreadsheets submitted with the proposal shall contain active formulas that enable the Government to trace price development from hours, rates, dollars, burdens, escalations and fee to the bottom-line price. The Offeror shall not remove the functionality of the Excel spreadsheet.

3. The Offeror shall submit cost summaries by Contract Fiscal Year (CFY) and GFY.

4. Within the Cost Reimbursement data, proposed hours, rates, resulting costs, and fee shall be broken out by month over the entire Contract PoP.

5. A summary table listing all labor categories used in the proposal and the associated direct labor rates by month, along with proposed escalation factors for the entire Contract PoP.

The Offeror shall identify the month in which rates are updated each year.

6. A summary table listing all indirect rates used in the proposal and the cost basis by month for the entire PoP. The Offeror shall identify the month in which rates are updated each year.

7. Proposed profit/fee percentages shall be identified by element of cost (e.g., prime labor, subcontractor labor, materials).

Direct Labor

This section shall address, but not be limited to, the following:

1. Identify the CFY schedule (e.g., start month and end month).

2. Include a table of all direct labor rates proposed by CFY.

3. Submit the latest copy of the Forward Pricing Rate Agreement (FPRA), Forward Pricing

Rate Recommendation (FPRR), or Forward Pricing Rate Proposal (FPRP) letter as available.

4. If other than standard bidding rates are used, the Offeror shall include a detailed explanation of why, and an appropriate means for verification of the proposed rates, including how the rates were calculated and a mapping of the proposed labor rates to the Offeror’s standard bidding rates. The use of composite rates is strongly discouraged and should be avoided.

5. Direct labor escalation factors and the basis for the proposed escalation rates shall be disclosed. Include a sample calculation demonstrating the application of the escalation factor to direct labor.

6. The Offeror shall identify the number of hours for a productive person-year per Full Time

Equivalent (FTE), in accordance with its Cost Accounting Standards Board (CASB)

Disclosure Statement.

Travel, Equipment, Material, and Other Direct Costs

The Offeror shall provide a costed and non-costed Bill of Materials (BOM) for evaluation by cost and non-cost evaluation panels. The Offerors BOM shall be proposed by SOW task. The BOM shall describe the material in terms defined by FAR 45.10, such as equipment, material, special test equipment, special tooling and other listing as needed and defined by FAR 45.101. These categories shall be separately listed and summarized. As an overarching statement the term

“material” is used in this paragraph to addresses the categories in the BOM in general.