Attachment 1 - PWS (Amendment 0004).pdf

Solicitation HQ085020R0004 Attachment 1 (Section C)

PERFORMANCE WORK STATEMENT FOR

SDA TRANCHE 0

MISSION SYSTEMS ENGINEERING & INTEGRATION

Dated July 30, 2020

1. Scope and Background

The National Defense Strategy (NDS) acknowledges that space is vital to the U.S. way of life, our national security, and modern warfare. In an era of renewed great power competition, maintaining our advantage in space is critical to winning these long-term strategic competitions. Potential adversaries seek to undermine this goal by employing strategies that exploit real or perceived vulnerabilities in our current and planned National Security Space systems. In addition, these potential adversaries are developing and demonstrating multi-domain threats to national security much faster than we can deploy responsive space-based capabilities. The Department of Defense (DoD) established SDA on 12 March 2019 as a separate DoD agency under the control, direction, and authority of the Under Secretary of Defense for Research and Engineering as a response to this problem.

SDA is responsible for defining and monitoring the Department's future threat-driven space architecture and accelerating the development and fielding of new military space capabilities necessary to ensure our technological and military advantage in space for national defense.

To achieve this mission, SDA will unify and integrate next-generation space capabilities to deliver the National Defense Space Architecture (NDSA), a resilient military sensing and data transport capability via a proliferated space architecture primarily in Low Earth Orbit (LEO). SDA will not necessarily develop and field all capabilities of the NDSA but rather orchestrate those efforts across DoD and fill in gaps in capabilities while providing the integrated architecture.

Initially the NDSA is comprised of the following layers, addressing the critical priorities for space identified within the DoD Space Vision:

• Transport Layer, to provide assured, resilient, low-latency military data and connectivity worldwide to the full range of warfighter platforms;

• Battle Management Layer, to provide architecture tasking, mission command and control, and data dissemination to support time-sensitive kill chain closure at campaign scales;

• Tracking Layer, to provide global indications, warning, tracking, and targeting of advanced missile threats, including hypersonic missile systems;

• Custody Layer, to provide 24x7, all-weather custody of time-sensitive, left-of-launch surface mobile targets (e.g., to support targeting for advanced missiles);

• Navigation Layer, to provide alternate position, navigation, and timing (A-PNT) for GPS- denied environments;

• Deterrence Layer, to deter hostile action in deep space (beyond Geosynchronous Earth Orbit (GEO) up to lunar distances);

• Support Layer, to enable ground and launch segments to support a responsive space architecture.

Organizationally, SDA is structured with product delivery cells (e.g., Transport Cell) focused on each of these functional capabilities, as well as an Emerging Capabilities Cell to incubate new functional capabilities and address emerging or evolving threats, such as a Deterrence Capability to deter hostile action in deep space, beyond GEO up to lunar distances.

SDA's mission begins and ends with the warfighter. SDA recognizes that sufficient or "good enough" capabilities in the hands of the warfighter sooner may be better than delivering the perfect solution too late. SDA will deliver capabilities to our joint warfighting forces in two-year Tranches.

Tranche 0, or the warfighter immersion tranche, will be delivered as early as Fiscal Year (FY) 2022 and consists of tens of satellites providing periodic, regional sensing and data transport capabilities, including the capability to detect hypersonic glide vehicles and to disseminate time- sensitive targeting solutions over tactical data links. SDA anticipates issuing separate solicitations for each of the capability layers in each Tranche.

Tranche 0 Overview

The Tranche 0 system consists of three major segments: Transport, Tracking, and Ground.

Launch will be provided through the Orbital Services Program 4 (OSP-4).

SDA released a Request for Proposals (RFP) on 1 May 2020 for its Transport Tranche 0 capability, an interoperable mesh network of satellites to provide periodic low-latency and high-capacity data connectivity over a given area of responsibility (AoR) and downlink over tactical data links. SDA intends to award up to four (4) firm-fixed price (FFP) contracts to build a total of 20 space vehicles for the Transport Tranche 0 capability. Specific requirements and technical challenges include but are not limited to low-recurring cost satellite buses, Link 16 and Integrated Broadcast System (IBS) mission payloads, and optical or RF interoperable crosslinks and networking.

SDA released an RFP on 15 June 2020 for its Tracking Tranche 0 capability. SDA intends to award up to two (2) FFP contracts to build up to 10 satellites that are interconnected with crosslinks with wide field of view (WFOV) infrared sensors for advanced missile warning and tracking. Specific requirements and technical challenges include but are not limited to low-recurring cost satellite buses, mass producible Overhead Persistent Infrared (OPIR) mission payloads and associated data processing, and interoperable crosslinks and networking. Two Medium Field-of-View (MFOV) systems will be launched separately by the Missile Defense Agency, and the goal is for WFOV and MFOV systems to provide complementary mission data to C2 and operational interfaces in Tranche 0.

The Ground segment will consist of two primary elements, Constellation Operations and Mission Operations. The Constellation Operations element provides day-to-day operation and maintenance of the constellation, including the tools and staff to manage the health and status of the constellation, the command loads, archiving telemetry, anomaly resolution, and all the typical functions of operating space systems. Constellation Operations for Tranche 0 is provided by the Naval Research Laboratory (NRL) via their Blossom Point Tracking Facility (BPTF).

The Mission Operations element is intended to comprise the mission-unique aspects of the system. This includes the external ground interfaces to Link-16 and IBS for both coordination and data transfer, as well as those to the OPIR enterprise and Custody partners.

Network topology management, payload scheduling, and data processing all reside in this element. The specific algorithms likely are provided by other cells within SDA, but these algorithms will be hosted within the Mission Operations element, and their integration together within the element, as well as with the larger ground segment and other segments, is a critical system engineering task for the success of Trance 0. Aspects of the Mission Operations will also be provided by or hosted by NRL.

Objectives

The SDA recognizes that the products (Space Vehicles, Ops Centers) under contract within each of the product delivery cells, and external partner activities/programs, need to be integrated in order to meet our mission objectives. The role of the MSE&I Contractor is to provide the infrastructure and effort required, under Tranche 0 Program Office direction, to ensure that:

(a) The Tranche 0 Tracking, Transport, and Ground Segments operate in unison to support Warfighter mission scenarios and experiments;

(b) The Ground Segment Elements function as an integrated entity providing telemetry, tracking and commanding (TT&C), mission data uplink/downlink, mission planning and payload tasking, constellation operations, and network management in support of Tranche 0 on-orbit demonstrations;

(c) System, cross-Segment, and external dependencies and interfaces are understood, documented, and managed;

(d) Systems engineering support is provided to Tranche 0 system-level and segment-level systems engineering activities so that they have support beyond what is provided by the space vehicle (SV) and ground contracts;

(e) Gaps in support for launch operations, mission operations, security, information technology (IT), and other areas have a means for closure;

(f) Tranche 0 Ground and Mission systems are integrated under a single lead organization, the MSE&I Contractor.

It is the intent of the SDA to allow the MSE&I Contractor considerable flexibility in terms of the approach used in meeting these objectives and the Government’s requirements as stated in this Performance Work Statement (PWS). The Contractor must, however, document the approach, e.g., via a Systems Engineering and Integration Plan and submit for within 30 days of contract award.

Tranche 0 MSE&I Challenges

Entering into the MSE&I role at this stage of the Tranche 0 program presents a number of special challenges. Among the most significant are:

(a) Developing and implementing a holistic mission system engineering and integration program that accounts for, and limits the impact to, the SV contracts and Government mission partners;

(b) Ensuring, using a lean, low-cost approach, the compatibility and interoperability of all elements of the SDA system and segments;

(c) User/Mission integration onto the Tranche 0 system where technical capability is significantly predetermined and the schedule is short;

(d) Holding schedule while providing a “minimum viable product” that enables the warfighter to experience the system’s unique capabilities in real scenarios and provides SDA insight into how the product should evolve;

(e) Capturing key lessons learned and other information which will form the basis for system requirements to be implemented by Tranche 1 and beyond;

(f) Managing effort with Government to Government relationships at key interface or deliverable.

SDA Partner Integration

In order to bring the most capability in the shortest time to Tranche 0, SDA has entered into agreements with, or anticipates agreements with, a number of Government entities. The MSE&I Contractor will need to work with these partners to integrate the Tranche 0 system.

Among these are:

The Naval Research Laboratory (NRL) – The NRL will provide:

(a) The hardware-in-the-loop/software-in-the-loop (HITL/SITL) testbed will be Government-owned and operated. It will be used to verify spacecraft and payload interoperability, network and routing behavior, space-to-ground site link compatibility, and space-to-space link compatibility and to perform software testing verification of the integrated command & control applications;

(b) Blossom Point Tracking Facility (BPTF) - The SDA Tranche 0 SV(s) will be operated from the NRL BPTF. Initial launch and checkout operations may be accomplished from a Contractor facility or from BPTF. If accomplished at a Contractor facility, operations will be transferred to BPTF for operations once initial launch and checkout is complete. The ground system at BPTF is designed to support SV TT&C and some mission data processing. It will be used for both initial and long-term test, experimentation and nominal SV operations;

These facilities will have the ability to communicate with the SVs, perform SV operations (nominal ops, orbit adjustment, recovery, de-orbit, software and data uploads), perform network operations (routing table generation with autonomous network implementation, software defined radio (SDR) update generation), and mission planning in support of Tranche 0 demonstrations/exercises. The BPTF uses vendor-provided command-telemetry databases, operations handbooks, etc. to operate the heterogeneous constellation without enforcing complete consistency on the SV-ground data interface.

N2N6/Naval Integrated Fires Element (NIFE) – Existing capabilities within the NIFE will be utilized in conjunction with Tranche 0 data products and transport network to demonstrate new capabilities. MSE&I integration activities will likely include development of interface definitions, interface control documents and specifications, detailed CONOPS, requirements analysis, assessment of resource/logistics support requirements and coordinating implementation of these interfaces and capabilities.

OPIR Enterprise – The SDA WFOV program (and potentially MFOV) will need to transmit mission data to the OPIR enterprise in compliant data formats.

TITAN, Others – SDA is exploring interfaces with the Army’s “TITAN” program and there will likely be several other programs in which a Tranche 0 integration would have potential benefits to warfighter.

Key System-level Areas of Expertise

In order to successfully deliver the services required by the SDA for Tranche 0, the MSE&I Contractor will need to demonstrate a team with the following key areas of expertise:

(a) Spacecraft systems, development, testing, and operations;

(b) Mission operations integration including ground segment elements: satellite, network, and mission operations centers;

(c) Integration of new technologies into warfighter environments, systems, system interfaces, operations, and engagement exercises. This includes planning, demonstrations, accreditations, and logistics;

(d) Network engineering, (satellite) equipment, protocols, security, interoperability, and (ideally) free-space optical comms;

(e) IT networks and their unique application to satellite constellations, ground entry points, and supporting ground networks and facilities;

(f) Ground and space system software architectures, development and verification methods, tools and practice in the context of distributed mission applications;

(g) Tactical communications systems including Link-16 and IBS message transmission and handling;

(h) Operations security, cybersecurity and cryptology methods, threats, and mitigations applied to DoD facilities, space systems, ground stations, and supporting facilities and systems;

(i) Implementation/use of systems engineering methods and tools in rapid prototyping environments;

(j) Flexible and efficient resource (particularly personnel) management in support of SDA Tranche 0;

(k) System integration and integration in context of evolving program with multiple major contracts;

(l) DoD and Intelligence Community (IC) policy, practices, and standards and related to space systems and supporting ground systems.

(m) Planning and execution of complex, integrated tests and experimentation to demonstrate and validate enterprise-level objectives and concept of operations (CONOPS)

SDA Organization & Locations

SDA is the acquisition agent for programs and systems that comprise the SDA Tranche 0.

SDA manages acquisition, sustainment, and future planning of multiple space‐based capabilities, payloads, and associated ground systems for the DoD. SDA activities occur at a variety of locations, however, the primary work location for the MSE&I Contractor is at their own facilities i.e., the Contractor is not required to collocate with the SDA.

SDA locations include:

• Primary duty locations at the Pentagon, VA and Crystal City, VA;

• SDA satellite offices are located at Redstone Arsenal, AL, Patrick AFB, FL, Los Angeles AFB, CA, and Schriever AFB, CO;

• On‐site integration, test and operations at Blossom Point Tracking Facility, MD, Naval Research Laboratory, Washington DC, Schriever AFB, CO, Buckley AFB, CO, Cape Canaveral AFS, FL, Vandenberg AFB, CA, and other CONUS locations TBD and world-wide monitoring stations.

During the performance of this contract, the MSE&I Contractor will be required at times to travel with the Government team to locations listed. Travel to other locations as requested by the Government may also be necessary.

Space Vehicle Contractor Locations - The Contractors for SDA have not yet been selected, but will consist of US-based companies.

2. Applicable Documents

Documents are provided for compliance or reference. Compliance documents are specifically noted below.

SDA documents

• SDA-specific documentation can be found in the MSE&I Bidders Library.

Processes and standards

• DoDI 8500.01, Cybersecurity, March 14, 2014 (Compliance)

• DoDI 8510.01, Risk Management Framework (RMF) for DoD Information Technology, March 12, 2014 (Compliance)

• DoDI 8580.1, Information Assurance in the Defense Acquisition System, July 9,

• DoDI 8581.01, Information Assurance Policy for Space Systems Used by the Department of Defense, June 8, 2010

3. Definitions

Elements. Major subdivision of each segment. Examples are individual space vehicles and the Constellation Operations element of the ground.

Enterprise. Encompasses everything related to the SDA-developed architecture.

Mission. User objectives for individual mission areas (e.g., transport, tracking, and ground) or a combination of mission areas.

Mission Integration. Integration of aspects of several mission areas required to support a broader mission. An example of this is a mission where coordinated OPIR collection and geographic distribution of transport nodes, network status/configuration, ground-based OPIR data processing availability, and geographic position and allocation of Link-16 tactical terminals are required to achieve success.

Segment. Consists of the ground segment and each “layer” of space vehicles.

System. The complete set of space vehicles and the associated ground segment at a defined point in time. The Tranche 0 system, as discussed below, consists of tracking and transport and the ground segment. Future Tranches will include SVs from multiple Tranches simultaneously.

System Integration. System-level integration of (mostly) physical components of the tracking, transport, and ground segments. This includes interfaces, performance requirements that have dependencies across the segments, risk dependencies, schedule dependencies, and distribution of requirements and deliverables needed for system-level or end-to-end testing, demonstrations, and other verification activities.

Systems Engineering Processes and Tools. The foundational processes needed to perform mission and systems integration and to capture, validate, maintain, and distribute the mission and system baselines.

Technical Baseline. Mission and system-level baseline as defined by controlled documentation and/or systems (e.g., a database or model). This includes, for example, mission use cases, controlled interfaces with internal and external entities, ICD, specification, validation and verification plans, and system defining software and communication requirements. The baseline will be defined to the lowest level needed to understand system dependencies (e.g., segment, elements, or components, as needed) and monitor or control changes to these dependencies via ICDs or specifications.

Tranche. The complete set of changes to the system associated with deployment of a set of SVs. Tranche 1, for example, would include the new transport and tracking SVs, any removal of Tranche 0 SVs, possibly new segments, and the changes to the ground segment associated with all of these modifications.

Additionally the “Contractor” implies “The MSE&I Contractor.”

4. Task Descriptions

This section of the PWS contains descriptions of the tasks to be performed by the MSE&I Contractor. These can be divided into tasks that define, modify, and control the Ground, System and Mission (technical and operational) baselines with the MSE&I Contractor providing the means to understanding the baselines, identifying gaps and issues, and closing those gaps when possible either by performing the work directly or via subcontracts.

General Tasks

(a) The Contractor shall document, maintain, and distribute (as needed) all results from evaluations, assessments, analyses, simulations, trades and reviews performed as part of this contract;

(b) The MSE&I Contractor shall provide and maintain all data separation for documents to avoid any potential Organizational Conflict of Interest (OCI) and International Traffic in Arms Regulations (ITAR) concerns;

(c) The Contractor shall be capable of utilizing and maintaining data at various classification levels up to an including TS/SCI and SAP.

4.1. Mission Integration

Mission integration, as defined here, is the process of assessing the capabilities planned for Tracking, Transport as well as some of the potential Custody and aPNT capabilities, and how these interact with each other and with the ground architecture, and then developing and implementing a plan to ensure that the combined system will be able to support these capabilities as well as key SDA missions.

Central to this is the integration of the Ground Segment mission systems. Mission operations (demo and other flight test planning) has a direct interface with the Warfighter and brings together the Tranche 0 OPIR capabilities, mesh network capabilities, low-latency high-bandwidth optical link capabilities, network management, tactical communications, mission planning, and the DoD elements already conducting critical warfighter missions.

For Tranche 0 the mission is defined at a high level by warfighter “Capstone” demonstration requirements. These requirements need to be refined, flowed to Segments, gaps identified, and CONOPS refined based upon expected Segment capabilities.

To this end, the Contractor shall:

(a) Lead the Capstone (Mission) detailed design, analysis, planning, and integration activities;

(b) Develop a detailed Mission Operations integration plan in coordination with NRL, specified DoD operation entities, the SV Contractors, and other stakeholders;

(c) Work with these stakeholders (Segments, Users, Partners) to define operational details, lower-level use cases (mission elements or components), requirements, interfaces, and controlling documents. These details shall be evaluated for interdependencies, risks, and redundancies;

(d) Evaluate the demonstrations, simulations, and testing required to demonstrate mission capability and document the interfaces, internal and external operations and resources required to successfully accomplish them. The Contractor shall support the development of planning documents, memorandums of agreement or understanding, and any other contractual agreements required.

Note: The Tranche 0 schedule and contractual arrangements will likely not support time/effort or information intensive methods such as models based systems engineering or full DoD Architectural Framework (DoDAF) architectural wiring diagrams. SDA is amenable to any approach that efficiently meets the requirements without a time-consuming development of SE tools.

Additionally, the Contractor mission integration activity must address, at least, the development of the following:

(a) A Concept of Operations (CONOPS) for each system and segment mission (e.g., use case or thread;

(b) Architectural and technical schematics showing interactions (e.g., operational functions, data, physical connections, and timing) among the Tranche 0 segments and their various elements;

(c) Risk reduction activities and end-to-end demonstration plans coordinated with the Segments and segment elements;

(d) Information mapping mission capabilities to System and Segment requirements and verification activities.

4.2. System Integration

The Contractor shall develop a Systems Engineering Management Plan (SEMP) and execute tasks accordingly. The contents of this plan shall be proposed by the Contractor.

The SEMP should address the establishment (derivation and documentation) and maintenance of the System technical baseline, the integrated system schedule, system risks, and other activities where coordination at the System level might be more effective than a stove-pipe approach at the Segment level.

General System Integration Tasks

Contractor shall:

(a) Identify and assess instances when cost, schedule, risk and technical baselines are not aligned or when baselines or products are not in compliance with the change control actions;

(b) Identify, manage and coordinate issues (e.g., hardware/software/ interfaces/timing between segments) to closure;

(c) Identify and resolve issues that arise during Segment Program and Tranche 0 events, meetings, and boards.

Schedule Integration

The Contractor shall:

(a) Deliver and maintain a Tranche 0 Master Schedule integrated with appropriate links to the Segment delivery schedules reflecting integration specific tasks, programmatic interfaces, System task interrelationships, deliverables, and system/Tranche 0 integration activities on a commercially available scheduling system;

(b) Identify and report on critical paths (e.g., first, second, and third tier), risks to these critical paths, and schedule drivers, and work issues to closure with all affected parties;

(c) Maintain a Giver/Receiver list coordinated with each segment and external partners;

(d) Evaluate SV Contractor plans and schedules for disconnects between programs, develop closure plans, work with stakeholders to resolve issues, use integration forums to request Government decisions needed to close issues, and report on issue closure.

Technical Baseline Integration

The technical baseline provides a configuration managed common understanding of the technical aspects of the Tranche 0 System and its Segments and external interfaces. These tasks are roughly time phased into:

(a) Baseline Establishment: Initial definition and recording of interfaces, requirements, specifications, physical and functional features, and mapping to mission capabilities (provided by Mission Integration tasks);

(b) Baseline Management: After SDA approval of the initial baseline the defining data is configuration managed to assure stakeholder concurrence with changes and promulgation to associated documents and activities;

(c) Baseline Evaluation, Validation and Verification: Collection of activities designed to extract information from the baseline data e.g., risks and technical gaps, and to assure the developed systems will deliver the required baseline capabilities.

Baseline Establishment

The Contractor shall:

(a) Establish the Tranche 0 technical baseline including all cross-space and ground segment interfaces and to lower levels only for interfaces considered to be key to inter- or intra-segment interoperability;

(b) Support baseline development for the Segments by drawing upon available CONOPS, contract statements of work, lower-level requirements, ICDs and other authorized documentation. Identify disconnects between segments and external agencies, and work the issues to closure;

(d) Develop and maintain use cases, mission threads, and operational scenarios mapping to SDA end‐to‐end systems requirements and verification;

(e) Create, define, deliver, and maintain a minimal set of architecture products (e.g., a subset of DoDAF-like products) necessary to perform mission and system integration across the segments and Contractors;

(f) Develop system and segment level requirements that allow the SDA Tranche 0 and Users to effectively and efficiently interoperate and submit the requirements to the change process.

Baseline Management

The Contractor shall:

(a) Establish a formal (baseline management) process for capturing the baseline and managing changes and distribution. Employ this process to identify, control, maintain, make recommendations to evolve, and execute changes, upon approval, to technical baselines;

(b) Use change management software to mitigate the risk of unauthorized and unplanned changes to the technical baseline, including document content and the associated links;

(c) Provide user access to all databases used to manage the Tranche 0 technical baseline whether hosted on MSE&I Contractor‐owned or Government‐owned servers;

(d) Analyze proposals, changes, and modifications to the current architecture to determine the impact on technical baselines, schedules, and other activities for which the Contractor has responsibility. Perform requirements analysis in response to requested changes, addressing flow‐down, and changes to systems engineering products such as ICDs and verification plans;

(e) Maintain interface control for all ICDs/ISs that involve interaction between segments, contractors, or external agencies. Where a SV Contractor has controlling authority for a particular interface, the MSE&I Contractor shall be responsible for influencing and coordinating the evolution of the interface but shall not be responsible for controlling the interface;

(f) Upon request from the Government, perform an impact analysis of any SV Contractor engineering change proposal (ECP) or proposed requirements or interface changes, including impacts to external stakeholders;

(g) Document the verification method and associated verification artifacts. Verification artifacts are defined as attributes that contain verification status, comments, and references to the evidence of verification (e.g., test reports, analysis);

(h) Contractor shall organize, facilitate and provide agendas, briefings and minutes for all Tranche 0 and segment level CM‐related boards, forums and working groups;

(i) Develop, maintain, coordinate and obtain SDA approval for system‐level technical performance measures (TPMs), as appropriate to current program phase and tasks across the system. Develop, monitor and assess these TPMs, including margin planning and tracking, and provide assessments to support program reviews, design reviews, key decision points, test readiness reviews, certification activities, and operational test activities.

Baseline Evaluation, Validation and Verification

The MSE&I Contractor shall:

(a) Utilize the Tranche 0 Technical Baseline in order to evaluate system level single point failures, risks, redundancies, opportunities, and capabilities;

(b) Develop and implement a comprehensive System-level Test and Evaluation (T&E) master plan that will be used to validate the Tranche 0 System capabilities and resolve critical operational and System technical issues;

(c) Assure that the System T&E plan is focused on minimizing the time and resources required and minimizes duplication of the verification activities planned for the Segment-levels;

(d) Identify specialized T&E capabilities, resources, and instrumentation requirements necessary to support Tranche 0 T&E activities throughout the system life cycle.

Determine if equipment or other resources from lower level verification can be utilized in lieu of new developments or procurements;

(e) Provide supplemental test and verification support to integrated System test activities.

Provide dedicated personnel as required to support test plan development, procedure development, test requirements analysis, equipment procurement, test performance, results analysis, and documentation;

(f) Prepare, maintain, and lead implementation of a System Requirements Verification Plan (SRVP) for Tranche 0 system‐level ICDs, specifications, interoperability requirements, and inter-Segment compatibility where SDA is responsible for requirements verification. This plan will describe the process to be followed to verify each system‐level requirement and what verification artifacts will be used to document the verification;

1. Model, simulate, analyze, test, and perform other system level verification activities to ensure that end‐to‐end performance is sufficient to satisfy functional, capability and performance requirements and report the results of all system level verification activities;

2. Support Segment modeling and simulation activities associated with requirements verification. Ensure all system modeling and simulation used for requirements verification and system certification are verified, validated, and accredited;

3. Ensure that valid test measurements and data acquisition methods are used in the reporting of test results.

(g) Report issues and impacts with the SV Contractors’ RVPs, recommend potential courses of action and work to closure all approved closure plans.

4.3 Ground Segment

The Tranche 0 Ground Segment is in the early stages of development with only high-level requirements and interfaces defined at the System-level and by the mission use cases. To support further development of the Ground system, the MSE&I Contractor shall:

(a) Lead efforts to perform System-level requirements development, requirements flow-down, interface design, integration, and verification;

(b) Work with the Ground Segment and NRL engineers to develop solutions incorporating the requirements of the other Segments and externals such as:

Custody algorithm hosting;

L-16 and IBS message generation, encapsulation, and routing;

Ground segment interface into mission data processing enterprise;

External interface management;

Payload planning, scheduling, and tasking.

The MSE&I Contractor shall determine where gaps exist and perform trades to determine options including potential performing or subcontracting for the work. Other ground segment integration tasks are already captured in the Mission Integration and System Integration sections.

Constellation Management Software

As required/directed, the Contractor shall develop, verify, and integrate algorithms and software designed to generate Constellation Management plans and scripts. These shall be designed to interoperate with the NRL TT&C ground software (Neptune®) and each of the Tranche 0 Space Vehicles. Primary functions include SV upload and software & hardware configuration management, orbit management (maneuvers), fault response and emergency operations.

Network Management Software

As required or directed, the Contractor shall develop, verify, and integrate algorithms and software designed to establish, maintain and modify the SDA space-based communication network. These shall be designed to interoperate with Neptune®, the mission channels (if data modems and network controllers are accessible via ISLs), and each of the Tranche 0 Space Vehicles. The network software must be able to generate Network Management plans and scripts, generate routing tables (if used), monitor network status and quality of service, and implement fault response and emergency operation scripts.

4.4 Risk Management

(a) The MSE&I Contractor shall implement a system risk management program and organize, document, execute and evolve, make recommendations to evolve, and execute changes to the risk processes for the Tranche 0 system to ensure the

Government is prepared to make program decisions at the risk board(s). The program shall consolidate cost, technical and schedule risk results to provide a cohesive representation of Tranche 0 risks;

(b) The Contractor shall organize and provide agendas, briefings and minutes for Tranche 0 System-level risk boards, forums and working groups;

(c) The Contractor shall participate in the various Segment and (potentially) SV Contractors’ Risk Management Boards or equivalent, and review risks for impacts, recommend new risks if needed and report on problems with risks outside the SV Contractors’ control;

(d) The Contractor shall document risks and opportunities and update the data monthly for presentation at the SDA risk boards.

4.5 Mission Assurance and Safety

The Contractor shall perform the following Mission Assurance functions:

(a) Establish, lead, and maintain an external and system‐level discrepancy reporting process for all discrepancies such as those found during external and system‐level analysis and test activities and report the status of discrepancies to include resolution;

(b) Review Segment-level mission assurance and quality engineering products such as end-item data packages for completeness and identify issues that need to be understood and/or resolved at the System level.

4.6 Cybersecurity

In Tranche 0 the Government Ground Entry Points, the communications network, operations center facility and its information technology infrastructure is one system which the Government will accredit. The Contractor space segment is a separate system which the Government will accredit.

In Tranche 0 the MSE&I Contractor shall perform Information System Security Officer (ISSO) duties in support of the Government Information System Security Manager (ISSM).

The two information technology (IT) systems under cybersecurity assessment are the space segment (separate transport and tracking satellites) and the IT system that includes the ground entry points, the communications network and the operations center facility and infrastructure. ISSO functions shall support the ISSM to:

(a) Implement the Risk Management Framework per DoD Instruction 8510.01.

Implementation details will be determined as part of the systems engineering process;

(b) Allocate functional and performance requirements from the system level to the subsystem and component level in a manner that ensures cybersecurity is an inherent attribute of the design;

(c) Document interfaces with SDA and external programs such that there is alignment between adjacent programs’ cybersecurity pedigrees and risk postures;

(d) Maintain awareness of cybersecurity vulnerabilities in commercial or Government software;

(e) Monitor the allocation of cybersecurity provisions, including reporting requirements, to Subcontractors in a manner that sufficiently protects Government program information;

(f) Meet cybersecurity related duties on classified Information Systems as outlined in DoD Manual 5200.01, Volume 3;

(g) Develop and demonstrate a cybersecurity risk management plan adhering to National Institute of Standards and Technology Special Publication (NIST SP) 800- 37, “Risk Management Framework for Information Systems and Organizations: A System Live Cycle Approach for Security and Privacy;”

(h) Demonstrate cyberspace defenses on all development systems to include continuous monitoring capability, unauthorized penetration and exploitation testing; as well as lexicon and workflow as specified in NIST SP 800-137, “Information Security Continuous Monitoring;”

(i) Provide a cybersecurity monitoring and testing capability in accordance with DoDI 8560.01, “Communications Security Monitoring and Information Assurance;”

(j) Provide for vulnerability mitigation, incident response, and reporting capabilities to limit damage and restore effective service following an incident.

5. Program Management

The Contractor shall perform technical planning and resource management in order to develop a schedule, budget, and organize as required in response to customer needs, Tranche 0 program gaps, and other forcing functions. The output from this process shall include:

(a) Revised task plans, schedules, and estimated budgets and resource needs;

(b) Updated metrics used to assess the effectiveness of the technical effort and staffing activities;

(c) Updated Systems Engineering Management Plan;

(d) Assessment of technical plan dependencies on Stakeholder and external organization commitments / deliverables;

(e) Presentation of this data at monthly Program Management Reviews;

(f) Plan and control the technical, business, and program management efforts necessary to accomplish overall contract objectives in accordance with the PWS and established schedule;

(g) Provide processes for timely response to unexpected changes including SDA schedules, funding profiles, and resulting manpower levels;

(h) Provide for Government visibility into Subcontractor activities at the same level the MSE&I Contractor uses to manage the subcontract(s);

(i) Develop, update, and maintain a Contract Work Breakdown Structure (CWBS) to manage the cost of the contract, including Subcontractor deliverables;

(j) Monitor contract, subcontract, purchase order, etc. activity. Monitor the potential need for contract modifications and implement modifications as necessary;

(k) Include small business participation in contracts to the extent prescribed by this contract or greater;

(l) Establish and maintain Associate Contractor, non‐disclosure, and other agreements that may be required in support of contract activities;

(m) RESERVED;

(n) Develop and execute a contract safety plan in accordance with MSE&I Contractor best practices and formats;

(o) Comply with the requirements of the DD Form 254 to include information protection, physical and personnel security processes to support unclassified and classified (including secret collateral and special access program) activities;

(p) Conduct all activities necessary for SDA compliance with the Clinger‐Cohen Act;

(q) Be responsive to SDA priorities with flexible emphasis in their management of the creation of the products described in this PWS;

(r) Respond quickly to Government requests for scope and cost reductions with recommendations that achieve the objectives in a manner that minimizes the risk to mission success;

(s) Close out this contract in accordance with Government direction as appropriate.

Government personnel and Government support contractors will frequently be present at the MSE&I Contractor's facility. The Government members will advise the MSE&I Contractor, review MSE&I Contractor efforts and provide clarification; however, the Government will not approve or disapprove the MSE&I Contractor effort. The accountability for the MSE&I Contractor effort is solely the responsibility of the MSE&I Contractor. The MSE&I Contractor shall not construe advice, reviews and clarifications by the Government members as direction by the Government. The Procuring Contracting Officer shall be the only individual authorized to redirect the effort or in any way modify any terms of this contract.

Startup to/from Incumbent and Prospective MSE&I Contractors

(a) The MSE&I Contractor shall perform startup activities such that there is minimal impact to SDA schedules;

(b) The MSE&I Contractor shall support any future transition to a new MSE&I Contractor during closeout of this contract.

Subcontractor Management

(a) The MSE&I Contractor shall provide sufficient Subcontractor leadership such that the performance to the Government is consistent between all participating Subcontractors;

(b) The MSE&I Contractor shall disseminate all lessons learned and quality improvements to all Subcontractors.

MSE&I Contractor Authority

The MSE&I Contractor shall not direct any Federally Funded Research and Development Center (FFRDC) or University Affiliated Research Center (UARC) contractors, SV Contractors or their Subcontractors. Only SDA has the authority to direct any contractors. Recommendations for any changes proposed by the MSE&I Contractor must be approved and executed by the Government.

MSE&I Contractor Issue Reporting

The MSE&I Contractor shall identify and report to the Contracting Officer’s Representative (COR) for resolution any situations that prevent the MSE&I Contractor from performing tasks and requirements in the PWS and which the MSE&I Contractor is unable to resolve internally.

Staffing Management

The MSE&I Contractor shall notify the Government prior to undertaking any change in key staffing assignments. The notification shall include the identification of the personnel involved, the expected duration, and a mitigation plan that shows that critical functions are not severely impacted.

5.1 Meetings

Program Management Reviews (PMRs)

The MSE&I Contractor shall host monthly PMRs, develop a proposed meeting agenda and submit for SDA approval, capture and track action items, and record minutes. The presented materials shall be sufficient to inform the Government of the status of and support discussions of approved agenda topics.

Task Order Kickoff Meeting

The MSE&I Contractor shall host a startup meeting within 21 calendar days of contract award or option exercise to review the output of the planning and transition as outlined in Section 4.1.1.

5.2 Task Order Deliverables

Engineering Status Reporting

The MSE&I Contractor shall:

(a) Establish effective audit, feedback, and tracking mechanisms for all engineering functions in this PWS, and prepare a weekly activity and progress report addressing the status of all engineering areas, even for those areas for which the Government retains responsibility to perform;

(b) Address (in the weekly activity and progress report) tracking of action items and suspenses; status of all work in process; upcoming projects or issues; all issues requiring direct Government participation or travel; past, current, and planned Temporary Duty (TDY), conferences and meetings, and related activities;

(c) Prepare a monthly activity and progress report in briefing format that summarizes significant engineering issues;

(d) Prepare the monthly report in a format and scope suitable for briefing to senior SDA management and will include the tracking of action items and suspenses; work in progress; upcoming issues; goals and projects; and past/current/planned TDYs.

Manpower Reporting

The MSE&I Contractor shall:

(a) Report Contractor labor hours (including Subcontractor labor hours) required for performance of services provided under this contract via a secure data collection site.

Reporting inputs will be for the labor executed during the period of performance for each Government fiscal year (FY), which runs 1 October through 30 September. While inputs may be reported any time during the FY, all MSE&I Contractor data shall be reported no later than 31 October of each calendar year. The MSE&I Contractor may direct questions to the Contractor Manpower Reporting Application (CMRA) help desk.

Uses and Safeguarding of Information: Information from the secure web site is considered to be proprietary in nature when the contract number and contractor identity are associated with the direct labor hours and direct labor dollars. At no time will any data be released to the public with the contractor name and contract number associated with the data.

5.3 Contract Administration

Training

The MSE&I Contractor shall have sole responsibility for training and supervising its personnel assigned to perform tasks under this contract. The MSE&I Contractor may also attend SDA and program‐specific training provided by the SDA and The Aerospace Corporation (only those courses open to contractors, as available) to gain a better understanding of the Tranche 0 missions, tools, and processes.

Supplies and Equipment

The MSE&I Contractor shall provide all supplies and equipment needed to successfully execute the requirements of this contract, unless otherwise specified in this PWS.

Duty Locations

(a) The Government performs at the primary and secondary locations identified in Sections above. The method for providing MSE&I support for the primary and secondary duty locations, i.e., utilizing local (based within close proximity of the assigned duty location) or remote (based outside close proximity to the assigned work location) personnel will be at the MSE&I Contractor’s discretion. Based on the needs of the Government, other locations may be added or deleted after award. The MSE&I Contractor should not assume that dedicated office space will be provided by either the Government or the SV Contractors. Requests for dedicated office space at the secondary locations only will be handled on a case by case basis;

(b) MSE&I Contractor personnel shall go on reimbursable business trips when directed by SDA to support their assigned responsibilities in this PWS.

Identification of MSE&I Personnel and Work Areas

MSE&I Contractor personnel, consultants, and Subcontractors shall identify themselves as MSE&I Contractors and Subcontractors in work areas during meetings, telephone conversations, in electronic messages, or correspondence related to this contract.

MSE&I Contractor Facilities and Infrastructure

The location of MSE&I Contractor personnel other than those specifically stated in the PWS and the personnel necessary to manage the facilities required by this PWS is at the discretion of the MSE&I Contractor and shall be consistent with the MSE&I Contractor’s overall strategy to provide responsiveness to real‐time needs of the SDA.

MSE&I Facilities within Proximity of the Primary Duty Location.

(a) The MSE&I Contractor is not required to maintain a facility near Government offices.

The primary work location for the Contractor is at their own facilities.

MSE&I Facilities at Secondary Duty Locations

(a) In non‐MSE&I Contractor‐operated facilities (e.g. Government (if approved) or SV Contractor facilities), MSE&I Contractor occupied/assigned offices, separate rooms, and cubicles shall be clearly identified with MSE&I Contractor‐supplied signs, nameplates, or other identification showing that these are work areas for MSE&I Contractor personnel.

Top Secret/Sensitive Compartmented Information (TS/SCI)/SAP Facilities

The MSE&I Contractor shall use secure facilities located at other locations that are identified as part of its overall strategy to provide responsiveness to real‐time needs of SDA.

(a) The MSE&I Contractor shall arrange suitable classified communications, networking, and meeting facilities to connect to its own secondary or remote facilities and Government sites;

(b) The room shall be configured such that it can be interchangeably used for multiple Special Compartmented Information /Special Access Required (SCI/SAR) programs;

(d) The MSE&I Contractor shall present a room certifiable under ICD 503 (for automated information systems (AIS)) and ICD 705 and submit a complete and detailed application package to the SDA to begin SAP facility (SAPF) certification.

Network Connectivity

(a) The MSE&I Contractor shall arrange for all PWS‐required network connectivity between the MSE&I Contractor’s facilities, Government and SV Contractor networks;

(b) The MSE&I Contractor shall provide network connectivity, which supports the use of Virtual Private Networks (VPNs), for Government and visiting contractors in rooms utilized by Government personnel (to include conference rooms and Government office space) or visiting contractors.

Tools

(a) For all technical and programmatic/management tasks and products accomplished under this PWS, the MSE&I Contractor shall ensure the use of tools and submitted data formats are approved by the Government, validated, compatible with Government tools, and that allow for the smooth transition of data to the next MSE&I Contractor.

5.4 Government Furnished Equipment, Property and Information

(a) It is not anticipated that there will be Government Furnished Equipment or Property associated with the MSE&I contract;

(b)…